<text>The syntax of the Scrunch function and of the Unscrunch function are identical. For example put scrunch(someText) into someScrunchedTextwould replace all the returns in the container someText with the special character. Likewise, put unscruch(someScrunchedText) into someText would put back where we started.Note: the special character normally used is option-L. This looks just like the line continuation character used by HyperCard in scripts. An optional second parameter allows you to override this default and use the special character you supply.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_61137.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 6003end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Miscellaneous Notes</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>UnScrunch</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Scrunch and its companion UnScrunch allow you to quickly "scrunch" multiple lines of text into a single line and then restore that text to its initial condition. This is accomplished by substituting all the return characters in the text with another, more innocuous one. This is convenient in a number of situations, most notably when you have to fit multiple lines of text into no more than one line of a container. A perfect example of this is when Dialoger returns the contents of an editable text field that contains returns. Since the whole organizing scheme of dResult depends on each item in the dialog taking up only one line, the text is Scrunch'ed before giving it to you. To restore it to its former multi-line glory, you will need to UnScrunch the text.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_60702.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>«name» is the name to be given the resource. If left empty, the resource will have no name.«id» is the desired id for the resource. Any existing resource will be replaced if it has the same name, otherwise a new resource will be made and given a different ID.The function's result «NewResID» is always the id of the newly created resource — unless an error occurred or the process of selecting a rect was canceled with cmd-.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_60636.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Within Dialog Maker there are three XFCNs which can be very useful for making graphic resources. They are all very similar, differing only in the kind of resource they make (pMaker = PICT resources, iMaker = ICON resources, sMaker = SICN resources). Each share a common format: put pMaker(«rect», «name», «id») into newResIDwhere:«rect» is the rectangle of the portion of the card to be used. If empty, you will be given the chance to define the rect on the screen. pMaker allows you to drag out the rect on using special cursors and a marquee while iMaker and sMaker give you a cookie-cutter cursor to choose the area.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_52501.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>One final note about explicit item numbering. Multiple commands may still be “stacked” in a single parameter (i.e. separated by a return). However, once an explicit item number has been specified in a parameter, it becomes the implicit one for other stacked commands in that parameter.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/27/90</text>
</content>
<name></name>
<script></script>
</card>
card_52234.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 10735end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Miscellaneous Notes</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Item Addressing</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Dialoger Professional still supports this syntax but adds the ability to explictly specify what item a command should affect. This is accomplished by preceeding any command with a “◊” (option-shift-V). This explicit item number will be used rather than the one implicit in the number of the parameter. For example, our previous change would look like this: dChanger dialog,"8◊True"This new syntax allows any item in the dialog to be changed - not just items 3 through 16. And any parameter may be used for any command (so long as it uses an explict item number). Commands to the dialog as a whole should use 0 as their item number (eg "0◊Modeless"). The sole exception to this is flexibility is substitution text which must appear first in parameter 2 (if at all).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_52012.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Previous versions of Dialoger supported only an implicit mapping between the number of the parameter in the call to Dialoger (or dChanger) and the item to be affected. In this scheme parameters 3 through 16 were for manipula-ting items 3 through 16 respectively. Parameter 1 was reserved exclusively for specifying the dialog and passing other commands to the dialog as whole. Parameter 2 was reserved exclusively for specifying the replacement text for static text items. This left items 1-2 and 16-? untouchable by Dialoger or dChanger. It also meant that if all you wanted to do was change item 8 (a checkbox) to true you would have to do something like this: dChanger dialog,"","","","","","","true"All those "",'s quickly became rather tedious.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_51748.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>A centralized error handler may now be specified for a dialog. This prevents “minor” errors from dismissing the dialog. Instead, this handler is called with the error ID of the problem. This capability is especially handy for palettes which might invoke scripts which use an “Exit to HyperCard” which is interpreted by HyperCard as an error. </text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_49936.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>It is very tempting to use color pictures in your dialogs to add some pizzaz. Unfortunately, a truly spectacular color picture usually looks like #$%@ on a black & white screen.Usually, therefore, it is preferable to use different pictures depending on how many colors the current screen can display. While Dialoger (and dChanger) can easily change pictures for you, it can't know when to do this, so its up to you to figure out when such swapping is appropriate.A handy little XFCN called DisplayColors helps with this decision. It returns the number of colors (including black and white) the main screen (ie the one with the menubar) is currently capable of displaying.Note: Color Quickdraw Macs using a screen in 1-bit mode return 2 just like Black & White Macs.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_45375.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput card field zz into itget Dialoger("A List", it)end mouseUp</script>
</part>
<part>
<id>2</id>
<type>field</type>
<visible> <true /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>301</left>
<top>68</top>
<right>501</right>
<bottom>153</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>zz</name>
<script></script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Miscellaneous Notes</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>ResIDNameList</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>When creating a list of labeled icons, you need to supply Dialoger with the IDs of the icons to be placed in the list and the label for each icon. If you would like to use the actual name of the Icon as its label, this can be accoplished very easily with ResIDNameList. This XFCN has the form: get ResIDNameList(«filename»,«type»)where «filename» is the name of the file whose icons you want listed, and «type» is the resource type you are interested in ("ICON" in this case"). If you omit «filename», all currently open resource forks will be examined.For example, to display a list of all currently available icons in the third item in you dialog (assuming it is a user item) you could say: Get ResIDNameList("","ICON")) Get Dialoger("A List","3◊userList Labeledicons"&CR&it)</text>
<text>When creating a list of icons, you need to supply Dialoger with the IDs of the icons to be placed in the list. This may accomplished using ResIDList, another XFCN included in the Dialoger package. This XFCN has the form: get ResIDList(<filename>,<type>)where <filename> is the name of the file whose icons you want listed, and <type> is the resource type you are interested in ("ICON" in this case"). If you omit <filename>, all currently open resource forks will be examined.For example, to display a list of all currently available icons in the third item in you dialog (assuming it is a user item) you could say: Get ResIDList("","ICON")) Get Dialoger("example","","userList icons"& CR & it)</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_10964.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>A popup menu item can be given a command-key equivalent by using the meta-character "/" and then the desired equivalent. For example, "Small/S" would make S the command-key equivalent for the popup menu choice "Small".Command-key equivalents are not case specific. However, for consistency’s sake, you should use the capital letter.Note: be sure you are not using a command-key equivalent which is already being used by HyperCard. While it may work, it is best to avoid the conflict. </text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Miscellaneous Notes</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1102</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_16211.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>A "(" before a menu item will make it disabled (ie it will be grayed-out and cannot be selected). A special use of this is to make a dividing line between sets of menu choices—like what divides Undo from Cut in the Edit menu. This is specified with a "(-" as a menu item.For example if we wanted a popup menu that looked similar to the Edit menu we could use the following: put "Undo" & return & "(-" & return & "Cut" & return…UserList items (using the Meta LDEF) may also use this meta character. The line containing this character will not be selectable from the list.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1101</text>
</content>
<name></name>
<script></script>
</card>
card_14635.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Even icons can be added to a menu item using the meta-character ^ followed by a digit 0..9. This digit plus 256 should equal the ID of the ICON to be placed in menu.For example a menu item specified as "^1Small" would be preceded by the ICON whose id was 257 (256+1).Note: if you run out of digits, you may also use letters, symbols, etc. To determine the ID which <char> represent, use the formula: ID = chartonum(<char>) + 208UserList items (using the Meta LDEF) may also use this meta character. Instead of an ICON, however, the subsequent digit identifies the SICN to precede the line.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1100</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_14099.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>To give a menu choice some style, include the character "<" followed by the first letter of the style you want (make sure it a capital letter). For example, "<B" anywhere in the text of a menu choice will cause that menu choice to be bold. Likewise, "<I" will cause it to be italic, "<O" makes it outlined, "<U" makes it underlined and "<S" makes it shadowed. These may be combined in any order for multiple styles (eg "<O<I<B"). Two styles you may be less familiar with are "<C" Condensed and "<E" Extended — these are also supported.Note: you must use upper case for the meta characters.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Miscellaneous Notes</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Meta Character</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1099</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_13909.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Thanks to the Menu Manager (another member of the Mac toolbox), you may spruce up you menu choices (and lists using the "Meta" LDEF) through the use of "meta-characters". These are characters which are not taken literally (they don't appear as part of the menu choice) but rather are interpreted as meaning something else. Each menu choice may have none, one or more of these meta-characters imbedded in text of the choice. Obviously, these characters only apply to the individual choice in which they appear.Using these meta-characters you can: assign text styles to individual menu choices, place icons before a menu choice, provide a keyboard equivalent to a menu choice, even disable a choice so that it may not be selected.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1098</text>
</content>
<name></name>
<script></script>
</card>
card_53636.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>In using this handler, be aware of two complications:If you set lockmessages to true before leaving a stack, the closeStack message is not sent and you will not clean up after yourself.The second is our same old probelm: If you leave the stack from within a hit handler, you will be pulling the rug out from under the dialog currently running. The result could be a rather spectacular crash. The reason for this is that once you leave the stack in which the dialog was opened, all the resources associated with that stack are no longer available. So when the Dialog Manager tries to display the dialog in a new stack it will not find the ICONs and PICTs and LDEFs, etc.that it needs and will complain bitterly (can you say "Crash and Burn").</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_22544.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This may be done with a closeStack handler such as the one below. This is not strictly necessary if you manage your dialogs very closely. Nevertheless, it is probably a good idea just in case you left one open. on closeStack … repeat forever get dContents() if it is not empty then dChanger it,"0◊Dismiss" else exit repeat end repeat … pass closeStack end closeStackThis script will look for any dialogs and dismiss them.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Non-Modal Dialogs</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>on closeStack</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1104</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_56305.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>It is important to note that this somewhat convoluted logic is only necessary when you are trying to implement sophisticated functionality which is triggered by a non-modal dialog. The rest of the time, simply using the hit handler will be both more efficient and less work.Nevertheless, the expedient of pulling logic out of the hit handler and putting it into a place where it can be invoked directly is often a best-of-both-worlds solution. It allows you to bypass the layer of complexity added by invoking it from the hit handler while debugging.I have made it all sound far more complicated than it is… but before I let you go, here is one more thing to think about: cleaning up when you leave the stack.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_56052.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text> on idle global msg2Send get Dialoger() if msg2Send is not empty then do msg2Send put empty into msg2Send end if pass idle end idleUsing this technique, you are no longer in Dialoger when the message "uglyProcess" is sent. This is especially handy for tool palettes like Dialog Maker's which kick off alot of scripts which have nothing to do with the dialog itself as these can be much more easily debugged. </text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_55561.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The idea is to make a stack-level handler out of the desired process — "uglyProcess" in our example below. Then, rather than directly invoking this handler from within the hit handler, the desire to have it called is queued in a global variable: on paletteHit dialog, itemHit global msg2Send … put "uglyProcess" into msg2Send … end palettHitThe idle script then looks at the global and kicks off the handler as needed. It would look something like…</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_55298.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The reason HC will die a horrible death when you leave the stack when executing a hit handler is that all the resources associated with the dialog (and perhaps Dialoger itself) reside in the stack you are in. When you leave, you pull the rug out from under Dialoger — all the components of the dialog are no longer where it expects them — and so it loses the will to live. You can alleviate this problem by making sure that all the needed resources are in the Home stack and not in the stack you are leaving but this is usually impractical since you won't "own" the Home stack.Another techniques alleviates all the problems associated with leaving the stack and also provides a more helpful development world — ie doesn't quelch the debugging messages HyperCard gives you. The cost is that it loads down your idle handler with another couple lines of scripting impacting performance slightly.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_55101.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Since all script activity initiated by a non-modal dialog is in the form of a hit handler, there are a couple of things to keep in mind when initiating complex processes:HyperCard is executing the hit handler (and any script the hit handler calls) while still technically "in" Dialoger. Afterall, it was Dialoger who sent the "hit" in the first place. While this situation can twist a mortal's mind beyond recognition, HyperCard handles it with remarkable aplum, allowing you to largely forget this distinction.However, it can come back to bite you in a couple of situations. 1) if you try and leave the stack while executing the hit handler, you will die a horrible death, 2) since you are in the nether relm of executing scripts from an XFCN, you will not get useful script error messages.Fortunately, there are work-arounds for both of these.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_20776.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>If you are trying to take an action whenever a non-modal dialog is dismissed, you will need to consider the following:If your non-modal dialog has a go-away box, that is one more way in which it can be dismissed (other than OK and Cancel). Although the Go-away box is not an item per-se, Dialoger, being helpful, notifies you of such an action by sending a hit with an itemHit of -1. If you need to take action after a dialog has been dismissed with the close box, then you should watch out for this case in your hit handler. The example at right demostrates this technique.A dialog may also be explictly dismissed with a call to dChanger. In this instance, no message is sent to the hit handler. However, since you are doing the dismissing, presumably you know what you are doing and why and what else must be done!</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script>on exampleHit dialog, itemHitif itemHit =-1 then -- Clicked goawayanswer "Shall I accept the order?" with "OK" or "Cancel"else if itemHit = 1 then -- OK clickedanswer "Order made. Throw in a pizza."else if itemHit = 2 then -- Cancel clickedanswer "Order canceled. Turn off oven."end ifend exampleHit</script>
</card>
card_54931.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Non-Modal Dialogs</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Modeless</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>The second part is responding to goings-on in a non-modal dialog. Notice that in the idle script there is absolutely no indication as to what dialog is begin run by Dialoger — or even whether there are any beging run at all.So, rather than using the idle handler, simply use a hit handler for any non-modal dialog. This handler will be called whenever something interesting happens in the dialog. This means that instead of processing the contents of the dialog after it has been dismissed (ie after the call to Dialoger), you process it whenever an interesting item is clicked (ie in the hit handler). Try the example.Notice that the dialog is still displayed when the final "hit" is sent to the hit handler — it probably won't make a difference in your design but I thoought I would mention it. Other, more interesting implications are discussed next.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script>on exampleHit dialog, itemHitif itemHit = 1 then -- OK clickedanswer "Order made. Throw in a pizza."else if itemHit = 2 then -- Cancel clickedanswer "Order canceled. Turn off oven."end ifend exampleHit</script>
</card>
card_54628.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>How, you may be wondering, will we know when the user clicks on something in a non-modal dialog? The answer has two parts. Firstly, all non-modal dialogs (except orphan) require an idle handler in the stack script which contains the statement "get dialoger()". For example: on idle get Dialoger() -- enables non-modal dialogs pass idle -- you must pass idle along to HyperCard end idleThis script gives Dialoger the opportunity to run a dialog whenever appropriate. If you omit this script, non-modal dialogs will not respond to mouse clicks at all. Likewise, because the idle message is only sent when using the browse tool, non-modal dialogs will be "dead" while any other tool is in use (ie button/field/painting tools).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_54357.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>--Sample script for invoking "A Pal"--Created on Wednesday, March 14, 1990on mouseUpput Dialoger("A Pal", "0◊Float", "1◊PictButton 3,1,Push") into dResultif word 1 of dResult is "Error:" then answer dResultend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Non-Modal Dialogs</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Modeless</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>You ask for any one of these using the same-named command to the dialog in the call to Dialoger. For example: put dialoger("A Pal","0◊float") into myFloatwould make the palette float above the HyperCard window. Unlike a modal dialog, however, Dialoger does not sit there and wait for the user to finish with the dialog and return a report of the contents of the dialog. Instead, Dialoger displays the dialog and returns immediately. The dialog will stay there until explictly removed with a call to dChanger (eg dChanger myFloat,"0◊dismiss"), or until its go-away box is clicked. Notice that Dialoger returned the dialog's identifying number "myFloat" instead of the dialog's contents — this is true for all non-modal dialogs.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_54013.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>--Sample script for invoking "ProgressBar"--Created on Tuesday, March 20, 1990on mouseUpglobal theDialogput return into CRput Dialoger("ProgressBar", "0◊Orphan") into theDialogif word 1 of theDialog is "Error:" then answer dResultpassTheTimeend mouseUpon passTheTimeglobal theDialogrepeat with i = 0 to 100wait 2 ticksdChanger theDialog,"3◊"&iend repeatdChanger theDialog,"0◊Dismiss"&iend passTheTime</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Non-Modal Dialogs</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Modeless</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Orphan — Despite its forlorn name, this dialog is quite useful. Whereas all the other uses of dialogs are built around responding to something the user does, orphans are designed to accomodate those situations when you want to display a dialog and then go off and do something completely unrelated. Progress dialogs are a fine example. You don't need or want the dialog to respond to clicks or keystrokes, you just want it to lie there informatively but quietly. Orphan dialogs do just that.Note: you might wish you could have a progress dialog with, say, a Cancel button. Well, you can't. Since you are off executing some script (the work that is in progress), Dialoger doesn't have any opportunities to detect the fact that you clicked on a cancel button — so you'll never know.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_49775.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>--Sample script for invoking "A Pal"--Created on Wednesday, March 14, 1990on mouseUpput Dialoger("A Pal", "0◊Float", "1◊PictButton 3,1,Push") into dResultif word 1 of dResult is "Error:" then answer dResultend mouseUp</script>
<text>One of the more exciting features of Dialoger is its ability to display and manipulate non-modal dialogs. There are three flavors of such dialogs:Modeless — just like a modal one except that it wil stick around if you click outside of it (rather than just beep). This means that you can display multiple windows and have them all "usable" at the same time. When not active, these dialogs retreat behind all other windows (including the HC window). Floating — just HyperCard's own floating windoids, these windows remain on top of the HyperCard window always. Such windows are most often used as tool palettes but may really contain anything. The only limitation is that they never "see" what the user types so they should not contain editable text or expect keyscrolling of a list.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_62495.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>____________________________________«Title»This command specifi.e.s that the text which appears along the top of a userBox is to be «title».There is no automatic truncating of the title text so be sure it will fit across the top of the userBox. Also, you might want to add a space before and after the title to give it some "breathing room".____________________________________Color «color name»This command changes the color of the specified dialog item. Obviously, this change will only be apparent to users of a color monitor. «color name»may be one of the following: (Red,White,Blue,Green,Cyan,Mgenta,Orange,Black).The list's scrollbar is not affected by this command.____________________________________FillPattern «pattern name»This command allows you to specify the pattern in which the interior of a userBox is drawn. Normally this is none but may be changed to any one of the pre-defined names: (none, white, black, gray, ltgray, dkGray).Note: advanced users may supply a number instead which serves as the index number into the system pattern list (Type PAT#, ID 0). This offers a wider selection of patterns to choose from. The system pattern list may also be supplanted by creating a custom pattern lists with the same ID.____________________________________HideHides an item from vi.e.w. If the item already been hidden, it has no effect. StyledText items may not be hidden.Note: This command actually moves the item far off-screen.This command is also available in Dialoger.____________________________________PenMode «mode»This command allows you to specify the pattern transfer mode used in drawing a userBox. Normally this is Copy but may be changed to either any one of the pre-defined names: (Copy, Or, Xor, Bic, NotCopy, NotOr, NotXor, NotBic).____________________________________PenPattern «pattern name»This command allows you to specify the pattern in which the border of a userBox is drawn. Normally this is black but may be changed to any one of the pre-defined names: (none, white, black, gray, ltgray, dkGray).Note: advanced users may supply a number instead which serves as the index number into the system pattern list (Type PAT#, ID 0). This offers a wider selection of patterns to choose from. The system pattern list may also be supplanted by creating a custom pattern lists with the same ID.____________________________________PenSize «width», «height»This command allows you to specify the size of the pen used to draw the border of a userBox. Normally this is 1,1 (pixels).____________________________________RoundCorners «xRadius», «yRadius»This command allows you to change a userBox into a rounded rectangle by specifying the "roundedness" of its corners. «xRadius», «yRadius» describe the oval that is used to round the corners of the box. The larger the values, the more round the corners. ____________________________________ShowDisplays a previously hidden item or dialog. If the item had not been hidden, it has no effect.This command is also available in Dialoger.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>UserBox Commands</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1089</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/10/90</text>
</content>
<name></name>
<script>on openCardset style of bg fld "wisdom" to scrollingunlock screenend openCardon closeCardset scroll of bg fld "wisdom" to 0set style of bg fld "wisdom" to rectunlock screenend closeCard</script>
</card>
card_62320.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>____________________________________Add «start line», «count»«list lines»This command allows you to insert «count» «list lines» to a list beginning with «start line». If «start line» is not specifi.e.d, «list lines» are added to the end of the list. If «count» is not specifi.e.d, one line is added.____________________________________AnySelectionSets the selection logic of a list to allow any set of lines to be selected. With this logic, a new selection may be added by command-clicking while a shift-click is equivalent to dragging from the point of the first click. This setting is the default. (Since this is the default, this command would only be needed if the list had been changed previously).____________________________________Color «color name»This command changes the color of the specifi.e.d dialog item. Obviously, this change will only be apparent to users of a color monitor. «color name»may be one of the following: (Red, White, Blue, Green, Cyan, Mgenta, Orange, Black).____________________________________ContiguousSelectionSets the selection logic of a list to allow only one contiguous block of list lines to be selected at a time. With this logic, one or more lines may be selected by dragging through the list. However, lines may not be added to the selection; any new one deselects all previous ones.____________________________________Delete «start line», «end line»This command will delete from a list «start line» through «end line». If «end line» is not specifi.e.d, it is assumed to be the same as «start line».____________________________________Deselect «start line», «end line»Deselects the lines «start line» to «end line» of a list. If «end line» is not specifi.e.d, only «start line» is deselected. Note: Dialoger now automatically respects list selection logic. Therefore, it is no longer necessary to Deselect previously selected lines when changing the selection of SingleSelection or ContiguousSelection Lists — it will be done automatically.____________________________________DeselectText «text»Deselects the first line of a list which matches «text».Note: Dialoger now automatically respects list selection logic. Therefore, it is not necessary to Deselect previously selected lines when changing the selection of SingleSelection Lists — it will be done automatically.____________________________________HideHides an item from vi.e.w. If the item already been hidden, it has no effect. StyledText items may not be hidden.This command is also available in Dialoger.____________________________________KeyScrollThis command allows you to enable key scrolling for a particular list. This technique, similar to that used in the Open… and Save As… dialogs allows you to select list lines by typing. It is only appropriate with Single Selection lists and then only if the list is sorted. One or more characters may be typed and the closest matching list line will be selected.This command is also not appropriate with editable text items in the same dialog since it is ambiguous who should get the keystrokes.This command is also available in Dialoger.____________________________________New«list lines»This command removes everything from a list and then fills it with «list lines» where «list lines» may be one or more lines (starting with line 2 of the parameter).____________________________________NoSelectionSets the selection logic of a list to not allow any lines to be selected. With this logic, the list may still be scrolled but no lines may be selected at all.____________________________________Replace «start line», «end line»«list lines»Replaces the contents of «start line» through «end line» of a list with the contents of «list lines». If «end line» is not specifi.e.d, it is assumed to be the same as «start line». ____________________________________Select «start line», «end line»Selects from a list the lines «start line» to «end line». If «end line» is not specifi.e.d, only «start line» is selected. This command now respects the selection logic. ____________________________________SelectText «text»Selects from a list the first line which contains «text». (The matching is not case-sensitive).____________________________________SelFlags «Logic»Sets the selection logic of a list to «logic». This command should only be used by experi.e.nced programmers who have a good understanding of the selFlags in the list managers record. Mere mortals should contents themselves with the built in capabiliti.e.s of Dialoger (i.e. NoSelection, SingleSelection, ContiguousSelection and AnySelection).____________________________________SetDblClick «item»This command allows you to have a double-click on a list line treated just like it was a click on another dialog «item».____________________________________ShowDisplays a previously hidden item or dialog. If the item had not been hidden, it has no effect.This command is also available in Dialoger.____________________________________SingleSelectionSets the selection logic of a list to allow only one list line to be selected at a time. ____________________________________Swap «line a», «line b»This command will exchange the contents of two list lines. «line a» must be less than «line b».</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>UserList Commands</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1089</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script>on openCardset style of bg fld "wisdom" to scrollingunlock screenend openCardon closeCardset scroll of bg fld "wisdom" to 0set style of bg fld "wisdom" to rectunlock screenend closeCard</script>
</card>
card_62028.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>____________________________________Color «color name»This command changes the color of the specifi.e.d dialog item. Obviously, this change will only be apparent to users of a color monitor. «color name» may be one of the following: (Red,White,Blue,Green,Cyan,Magenta,Orange,Black).____________________________________HideHides an item from vi.e.w. If the item already been hidden, it has no effect. StyledText items may not be hidden.Note: This command actually moves the item far off-screen.This command is also available in Dialoger.____________________________________New«menu items»This command removes everything from a popup and then fills it with «menu items».____________________________________Select «menu item»Selects from a popup menu the item «menu item». ____________________________________ShowDisplays a previously hidden item or dialog. If the item had not been hidden, it has no effect.This command is also available in Dialoger.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>UserPop Commands</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1089</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script>on openCardset style of bg fld "wisdom" to scrollingunlock screenend openCardon closeCardset scroll of bg fld "wisdom" to 0set style of bg fld "wisdom" to rectunlock screenend closeCard</script>
</card>
card_61834.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>____________________________________«ID»This command changes the graphic (either an icon or a picture) to the resource of the same type whose id is «ID».This command is also available in Dialoger.____________________________________«Name»This command changes the graphic (either an icon or a picture) to the resource of the same type whose name is «name».This command is also available in Dialoger.____________________________________HideHides an item from view. If the item already been hidden, it has no effect. StyledText items may not be hidden.Note: This command actually moves the item far off-screen.This command is also available in Dialoger.____________________________________Select «part»Selects from a picture button (i.e. one made with the PictButton command) the part of the grid whose number is «part». Part numbers are assigned left-to-right and then top to bottom.____________________________________ShowDisplays a previously hidden item or dialog. If the item had not been hidden, it has no effect.This command is also available in Dialoger.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Graphic Commands</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1089</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script>on openCardset style of bg fld "wisdom" to scrollingunlock screenend openCardon closeCardset scroll of bg fld "wisdom" to 0set style of bg fld "wisdom" to rectunlock screenend closeCard</script>
</card>
card_61689.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>____________________________________«Text»This command replaces the contents of a text item with «text».If «text» is empty, the text item will likewise be made empty — except when the parameter is completely empty. For example, if item 3 were editable text, then dChanger dialog,"3◊" would empty the contents of the editable text item while dChanger dialog,"","" would not. Get it?This command is also available in Dialoger.____________________________________Font «fontName»This command changes the font of a text item to «fontName». This command only affects items which have been designated styled with the StyledText command.____________________________________FontSize «size»This command changes the size of a text item to «size». This command only affects items which have been designated styled with the StyledText command.____________________________________FontStyle «codes»This command changes various characteristics of a text itemaccording to «codes». This command only affects items which have been designated styled with the StyledText command.____________________________________HideHides an item from vi.e.w. If the item already been hidden, it has no effect. StyledText items may not be hidden.Note: This command actually moves the item far off-screen.This command is also available in Dialoger.____________________________________HideScrollThis command hides the scrollbar of a text item. This command only affects items which have been designated styled with the StyledText command.Select «start char», «end char»Selects some or all of the text in the editable text item. Select alone selects all the text. If «start char» alone is specifi.e.d, the insertion point (the blinking bar) is placed after «start char». If both «start char» and «end char» are specifi.e.d, characters «start char» through «end char» (inclusive) are selected.This command is also available in Dialoger.____________________________________ShowDisplays a previously hidden item or dialog. If the item had not been hidden, it has no effect.This command is also available in Dialoger.____________________________________ShowScrollThis command shows the scrollbar of a text item. This command only affects items which have been designated styled with the StyledText command.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Text Commands</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1089</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script>on openCardset style of bg fld "wisdom" to scrollingunlock screenend openCardon closeCardset scroll of bg fld "wisdom" to 0set style of bg fld "wisdom" to rectunlock screenend closeCard</script>
</card>
card_40120.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>____________________________________«Label»This command changes the label (also called the title or name) of the button or control to «Label».This command is also available in Dialoger.____________________________________ActivateActivates a previously Inactivated* button or control. If it has already been activated, it has no effect.* An inactive button or control does not respond to clicks. This condition is usually visually represented in some way (e.g. buttons are grayed-out).This command is also available in Dialoger.____________________________________DismissSpecifies that the button or control should dismiss the dialog when clicked. For your conveni.e.nce, Dialoger automatically designates items 1 (OK) and 2 (Cancel) as Dismiss buttons so this command is not needed for them. This command may be "undone" with the NoDismiss command. This command is also available in Dialoger.____________________________________HideHides an item from vi.e.w. If the item already been hidden, it has no effect. StyledText items may not be hidden. This command actually moves the item far off-screen.This command is also available in Dialoger.____________________________________FalseSets the button or control to false (i.e. not hilited). In the case of controls, false sets the value to 0. This command is also available in Dialoger.____________________________________InactivateInactivates* a button. An inactivated button appears grayed-out and does no respond to clicks. If the button has already been inactivated, it has no effect.* An inactive button or control does not respond to clicks. This condition is usually visually represented in some way (e.g. buttons are grayed-out).This command is also available in Dialoger.____________________________________Max «Max»Sets the maximum value of the custom control to «max».This command is also available in Dialoger.____________________________________Min «Min»Sets the minimum value of the custom control to «min».This command is also available in Dialoger.____________________________________NoDismissSpecifies that the button or control should not dismiss the dialog when clicked. Initially, this coomand is only needed for items 1 and 2 since they are the only ones which dismiss the dialog by default.This command is also available in Dialoger.____________________________________ShowDisplays a previously hidden item or dialog. If the item had not been hidden, it has no effect.This command is also available in Dialoger.____________________________________TrueSets the button or control to true (i.e. hilited).This command is also available in Dialoger.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Button Commands</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1089</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script>on openCardset style of bg fld "wisdom" to scrollingunlock screenend openCardon closeCardset scroll of bg fld "wisdom" to 0set style of bg fld "wisdom" to rectunlock screenend closeCard</script>
</card>
card_21209.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>____________________________________CancelItem «item»This command associates a cmd-. (command period) with clicking on item number «item». Initially, item 2 is the cancel item which should correspond to the Cancel button. This may be changed using this command to any other button or control. This command is also available in Dialoger.____________________________________DefaultItem «item»This command associates a RETURN or ENTER with clicking on item number «item». Initially, item 1 is the default item which should correspond to the OK button. This may be changed using this command to any other button or control. Note: An «item» of 0 may also be specified. In this case, RETURN will not be intercepted and may be entered into an editable text item. Since this would cause the result reporting mechanism to become confused, the RETURN characters are converted to a special character before being returned. They can be restored by using Unscrunch. For example, if item 6 was an editable text item which might contain returns, the following statement would retreive the information from dResult.put Dialoger("Example","0◊DefaultItem 0") into dResultput Unscrunch(line 6 of dResult) into theTextThis command is also available in Dialoger.____________________________________DismissThis command causes the dialog to be dismissed. If this command is given by dChanger in a Hit Handler script, the dialog will not actually be dismissed until the script ends and control is returned to Dialoger. The result that returned from Dialoger will reflect the fact that no pushbutton was clicked to cause the dismissal (i.e. no push button will return its name). If the dialog is not currently being run by Dialoger, then dChanger will dismiss the dialog immediately.This command is also available in Dialoger.____________________________________Font «fontName»This command changes the default font for the Dialog to «fontName». This affects all static and editable text items in the dialog (except those designated StyledText"). It will not affect the font used in any button or in any user items. This approach is preferable to using StyledText when there are more than a few text items which must all be in a font other than Chicago as there is less overhead than with StyledText.This command is also available in Dialoger.____________________________________Fontsize «fontName»This command changes the default font size for the Dialog. This affects all static and editable text items in the dialog. It will not affect the text used in any button or in any user item. This approach is preferable to using StyledText when there are more than a few text items which must all be in a font other than Chicago as there is less overhead than with StyledText.This command is also available in Dialoger.____________________________________Height «height»This command changes the height of the dialog window. «height» specifies the height in pixels of the dialog.This command is also available in Dialoger.____________________________________HideHides an item from view. If the item has already been hidden, it has no effect. StyledText items may not be hidden.This command is also available in Dialoger.____________________________________KeyScrollItem «item»This command allows you to enable key scrolling for the list whose item number is «item». This technique, similar to that used in the Open… and Save As… dialogs, allows you to select list lines by typing. It is only appropriate with Single Selection lists and then only if the list is sorted. One or more characters may be typed and the closest matching list line will be selected. This command is also not appropriate with editable text items in the same dialog since it is ambiguous who should get the keystrokes.This command is also available in Dialoger.____________________________________Loc «Top», «Left»This command changes the location of the dialog window. The coordinates «Top» and «Left» are global (i.e. with respect to the screen, rather than the HyperCard window).Embedded within the DLOG resource is information about the location at which the dialog should be displayed. Normally, Dialoger ignores this information and centers the window on the card window. To force dialoger to use this information specify a location of 0,0.This command is also available in Dialoger.____________________________________ShowDisplays a previously hidden item or dialog. If the item had not been hidden, it has no effect.____________________________________Title «new title»This command changes the title of the dialog to «new title». Since only dialogs with a title bar will display this change, it is meaningful only for such dialogs.This command is also available in Dialoger.____________________________________Width «width»This command changes the width of the window. «width» specifies the width in pixels of the dialog.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Dialog Commands</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1089</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script>on openCardset style of bg fld "wisdom" to scrollingunlock screenend openCardon closeCardset scroll of bg fld "wisdom" to 0set style of bg fld "wisdom" to rectunlock screenend closeCard</script>
</card>
card_19545.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to stack "dCommands"end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>In General</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>While these are two popular commands, they are by no means the only ones. In fact, there are almost fifty available in all. A comprehensive reference is provided in the Helper window of Dialog Maker. It presents each command along with notes on its use and an example.Just to give you a feel for the capabilities that await... the following cards provide a description of the commands available for each different type of dialog item.These commands may be "stacked" by placing multiple commands on different lines. For example, to make item 4 (a radio button) both "grayed-out" and true, you could: dChanger dialog,"4◊true" & return & "inactivate"</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1088</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/10/90</text>
</content>
<name></name>
<script></script>
</card>
card_19433.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Commands</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>What are these commands and what do they look like? Well, here is an example (using our trusty dialog again). dChanger dialog, "", "Dismiss"This would instruct the third item in the dialog (the push button "Motto…") to dismiss the dialog when it is clicked. Alternately, we might want to "gray-out" the button so that it cannot be clicked. That can be done with the command "Inactivate": dChanger dialog, "", "Inactivate"Notice from these examples that dChanger is an XCMD, not an XFCN which means that you do not put parentheses around the parameters.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1087</text>
</content>
<name></name>
<script>on example1Hit dialog, itemHitif itemHit = 0 then -- (no sense in doing it over & over)dChanger dialog, "", "Dismiss"end ifend example1Hiton example2Hit dialog, itemHitif itemHit = 0 then -- (no sense in doing it over & over)dChanger dialog, "", "Inactivate"end ifend example2Hit</script>
</card>
card_18933.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 22128end mouseUp</script>
</part>
<part>
<id>3</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>203</top>
<right>503</right>
<bottom>219</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>Substitution Text</name>
<script>on mouseUppush cdgo to card id 10735end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>dChanger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Now we are ready to get down to some heavy duty work. In our hit handler script we now know exactly what the dialog looks like at this moment (using dContents). The next step is to change the dialog in some way. We can make these changes with a new XCMD called "dChanger". Like Dialoger, dChanger can accept up to 16 parameters. Like dContents, the first parameter must always contain the dialog identifier sent to the hit handler by Dialoger. The second (just like Dialoger) accepts text to be used as replacements for the placeholders ^0 through ^3 in static text items.The third through sixteenth are commands to dialog items 3 through 16 (the same way Dialoger does it).</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1086</text>
</content>
<name></name>
<script></script>
</card>
card_18951.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>dContents‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Unlike a list, the contents of a popup menu is reported as the text of the menu item selected. For example, if menu item 2 of our example dialog's popup (which was item 11)was selected, then "dContents(dialog,11)" would return the text "Medium". Sometimes, however, it is desirable to get the menu item number rather than the text…Our third parameter allows us to do just that. Reporting by menu item text (the default) can be thought of as being the "long" form of reporting a popup selection. Accordingly, the "short" format may be requested by supplying the word "short" as a third parameter: put dContents(dialog, 11, "short") into dPopLinewill return the selected menu item of the popup.</text>
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<part>
<id>3</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>396</left>
<top>174</top>
<right>509</right>
<bottom>308</bottom>
</rect>
<style>rectangle</style>
<autoSelect> <false /> </autoSelect>
<showLines> <true /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>9</textSize>
<textStyle>plain</textStyle>
<textHeight>12</textHeight>
<name></name>
<script></script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>dContents‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Alternate List</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>This third parameter may also have the value "All" when requesting the contents of a list. This causes the entire contents of the list to be returned — irrespective of which lines where selected.For example: put dContents(dialog, 10, "all") into dTheListwill return the full text of the list which is in item 10.</text>
<script>on exampleHit dialog, itemHitif itemHit = 1 or itemHit = 2 then -- dialog is a gonerget dContents(dialog,10,"all")put it into cd fld 1show cd fld 1put "Waiting for your click…"wait until the mouse is downput emptyhide cd fld 1end ifend exampleHit</script>
</card>
card_19861.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput empty into cd fld 1show cd fld 1put "Small" & return &¬"Medium" & return &¬"Large" & return &¬"Ex Large" into PopUp1put "Anchovies" & return &¬"Hamburger" & return &¬"Mushrooms" & return &¬"Onions" & return &¬"Pepperoni" & return &¬"Peppers" & return &¬"Sausage" into List1put Dialoger("Example" & return & "on exampleHit"¬, "0◊Loc" && topLeft of cd window¬, "4◊true"¬ --Radio Button "Deep Dish", "7◊Any Name Goes Here"¬ --Editable Text "", "10◊userList meta" & return & List1¬ --List, "11◊userPop 1, 15" & return & PopUp1¬ --PopUp, "12◊StyledText New York,18,BU"& return &"Peter’s Pizza Palace"¬ --Text "Peter’s Pizza Palace", "13◊userBox" &return &" Style "¬ --Box (Black pen, None fill) " Style ", "14◊userBox Gray"¬ --Box (Gray pen, None fill)) into dResulthide cd fld 1end mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>149</top>
<right>503</right>
<bottom>169</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Card Script</name>
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<part>
<id>3</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>396</left>
<top>174</top>
<right>509</right>
<bottom>308</bottom>
</rect>
<style>rectangle</style>
<autoSelect> <false /> </autoSelect>
<showLines> <true /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>9</textSize>
<textStyle>plain</textStyle>
<textHeight>12</textHeight>
<name></name>
<script></script>
</part>
<content>
<layer>background</layer>
<id>5</id>
<text>Alternate List</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>dContents‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>As you may have noticed, the contents of a list is reported as the line numbers of the lines selected. For example, if lines two and five were selected from a list which was item 11, then "dContents(dialog,11)" would return "2,5". Sometimes, however, it is desirable to get the actual text of the lines selected, rather than their line numbers.Our optional third parameter also allows us to do just that. Reporting by line numbers (the default) can be thought of as being the "short" form of reporting list selections. Accordingly, the "long" format may be requested by supplying the word "long" as a third parameter: put dContents(dialog, 10, "long") into dSelListLineswill return the selected lines of the list (one per line).</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1084</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<content>
<layer>card</layer>
<id>3</id>
<text>AnchoviesMushrooms</text>
</content>
<name></name>
<script>on exampleHit dialog, itemHitif itemHit = 10 then -- the list was clickedget dContents(dialog,itemHit,"long")put it into cd fld 1end ifend exampleHit</script>
</card>
card_53281.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 50701end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>dContents‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Single Item</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Height The height of the dialog windowKind The kind of use the window is operating under. Possible values are Modal, Modeless, Float, Orphan and Doomed.Loc The location of the top left of the dialog window (relative to the top left of the screen)Ptr The unique number which identifies the dialog. This may also be obtained by passing dContents only the window's title (or nothing at all).Title The title of the dialog (even if the window doesn't actually display this title). Width The height of the dialog window</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_53185.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Just as Dialoger and dChanger interpret an item number of 0 to indicate the entire dialog, so too does dContents. So, put dContents(dialog, 0) into theTitlewould return the title of the dialog identified by dialog.As you might wish, there is more information available from dContents than just the dialog's title. To request one of these other nuggets of information, an optional third parameter is used. This parameters is one of the words presented on the next card which each returns the specified information. For example: put dContents(dialog,0,"Loc") into dTopLeftwould put the location of the dialog's window in dTopLeft.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_17480.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>6</id>
<text>Sometimes, you will just want to know the contents of a particular item in the dialog. Rather than making it examine the entire dialog, you may ask for the contents of just that item using the optional second parameter: put dContents(dialog, 5) into dItemResultAs you have already guessed, the optional second parameter is the number of a particular item. Since it only needs to contain a single item’s contents, dItemResult will consist of only a single line (ie item 5's contents will be dIntermResults, not line 5 of dItemResult).This form is often a useful shortcut. It is especially attractive when a long list is involved since the process of identifying all the selected lines can be time-consuming.</text>
<text>Actually dContents and dChanger both accept alternatives to the dialog pointer as the first parameter. If nothing (ie empty) is passed as the first line of the first parameter, the frontmost eligible dialog currently displayed will be used. Eligible implies only those windows created by Dialoger.If a name is passed as the first parameter, the frontmost eligible dialog currently displayed with that name as a title will be used. This works even if the title is not displayed (eg floating palettes.)Since you will normally be using these X's only within a hit handler these techniques will not be needed. They are less efficient than directly passing in the dialog pointer and should, therefore, only be used when necessary. </text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_22128.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 6003end mouseUp</script>
</part>
<part>
<id>4</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>396</left>
<top>162</top>
<right>509</right>
<bottom>308</bottom>
</rect>
<style>rectangle</style>
<autoSelect> <false /> </autoSelect>
<showLines> <true /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>9</textSize>
<textStyle>plain</textStyle>
<textHeight>12</textHeight>
<name></name>
<script></script>
</part>
<part>
<id>5</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>108</top>
<right>503</right>
<bottom>128</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Example</name>
<script>on mouseUpput empty into cd fld 1show cd fld 1put "Small" & return &¬"Medium" & return &¬"Large" & return &¬"Ex Large" into PopUp1put "Anchovies" & return &¬"Hamburger" & return &¬"Mushrooms" & return &¬"Onions" & return &¬"Pepperoni" & return &¬"Peppers" & return &¬"Sausage" into List1put Dialoger("Example" & return & "on exampleHit"¬, "0◊Loc"&&topLeft of cd window ¬, "4◊true"¬ --Radio Button "Deep Dish", "7◊Any Name Goes Here"¬ --Editable Text "", "10◊userList meta" & return & List1¬ --List, "11◊userPop 1, 15" & return & PopUp1¬ --PopUp, "12◊StyledText New York,18,BU"& return &"Peter’s Pizza Palace"¬ --Text "Peter’s Pizza Palace", "13◊userBox" &return &" Style "¬ --Box (Black pen, None fill) " Style ", "14◊userBox Gray"¬ --Box (Gray pen, None fill)) into dResulthide cd fld 1end mouseUp</script>
</part>
<part>
<id>6</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>132</top>
<right>503</right>
<bottom>152</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Card Script</name>
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>dContents‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Now that we have wrested control from Dialoger and are in our hit handler script, the first order of business would seem to be finding out what the dialog looks like at the moment. An XFCN, called dContents will do just that for us. In its simplest form, it returns exactly the same thing that Dialoger would — except the dialog doesn't go away. That means that if we say: put dContents(dialog) into dIntermResultthen line n of dIntermResult will contain the contents of item n of the dialog (at that moment in time).Notice we provided it with the parameter "dialog" — one of the numbers given to the hit handler as a parameter. It uniquely identifies the dialog we want the contents of.</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1082</text>
</content>
<content>
<layer>card</layer>
<id>4</id>
<text>falsetruetrueAny Name Goes Here2Medium</text>
</content>
<name></name>
<script>on exampleHit dialog, itemHitput dContents(dialog) into cd fld 1end exampleHit</script>
</card>
card_17176.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>One little note about scripting errors in hit handler scripts. When they occur (don't worry, everyone makes them), they will not be reported accurately. The reason for this is that when you call Dialoger, HyperCard thinks its job is done until a value is returned. Meanwhile Dialoger is executing your script behind its back. When something goes wrong, all HyperCard can usually manage is to tell Dialoger that something didn't work. Dialoger then informs you that something went wrong… but it doesn't know what.Now that you have the bad news, here is some more: there is no clever work-around. However, a technique which is sometimes helpful is to execute the hit handler directly by typing it into the message box (don't forget the parameters). Note that this will trip up when it encounters a call to an X which expects a dialog to be there.</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Bugs</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1081</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_16469.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>As you may have noticed, Dialoger also provides three parameters with its message. The first is a number which uniquely identifies the dialog. It will be used later by the X's which allow you to examine the contents of the dialog and to change it. The second is the number of the item which has been "hit" (0 signifies the initialization message). The third pertains only to picture buttons and controls.The script you write, therefore should include these two parameters so you can easily refer to them. For example, if you had called Dialoger with: get Dialoger("MyDialog" & return & "on myHit")then your script should begin with something like: on myHit dialog, itemHit, partHit</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Taking Control</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Hit Handling</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1080</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_9685.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpedit script of this cdend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>6</id>
<text>What is the message? Well, you get to pick. When you invoke Dialoger you may optionally specify the name of a message which to be sent when an item is "hit" (ie the "hit handler"). This is done by including the command "on «hit handler name»" in any line of the first parameter. For example: get Dialoger("example" & return & "on exampleHit")would instruct Dialoger to send the message "exampleHit" to the current card each time a dialog item is hit.Notice that Dialoger also sends the message once before anything has been clicked (even before the dialog is displayed) so that you can do any necessary initialization and make any final changes to the dialog itself before it appears.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Taking Control</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Messaging</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1079</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script>on exampleHit dialog, itemHitif itemHit = 0 thenput "Initializing Dialog…"else if itemHit = 3 thenanswer "“Hold the anchovies!”"else put "You just clicked on item " & itemHitend exampleHit</script>
</card>
card_18049.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Up until now, Dialoger has had exclusive control over the dialog while it is being displayed. Sometimes, however, it would be nice to have the dialog "react" to actions taken by the user. Happily, Dialoger provides a mechanism which allows you to intervene while the dialog is being displayed.It does this by reporting on each "action" taken by the user. Actually it reports on: 1) each mouseDown occurring in an item and 2) each keyDown when entering text in an editable text item. Together, these are referred to as "hits".This reporting takes the form of a message sent by Dialoger to the current card. You then write a "hit handler" to respond to the message which Dialoger sends. It is in this script that you can orchestrate changes to the dialog.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1078</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_34680.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpgo (short name of me)end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Your Done</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text> C O N G R A T U L A T I O N S You have completed the second section “Digging In”You now know enough to create and use your own dialogs!Use the stack button at right to explore the other parts of the Dialoger package, -- or --Continue on into section 3 “Getting Fancy” to learn about the more sophisticated aspects of Dialoger.</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1077</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<name></name>
<script></script>
</card>
card_24851.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Script:You may apply a single line of script to all the selected objects using this button. This can be used, for instance to change a property of all the selected objects. In the script line, refer to the object as obj. It will be translated appropriately. For example a script of "hide obj" would hide all the selected objects.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1076</text>
</content>
<name></name>
<script></script>
</card>
card_23741.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Position Change:This section allows you to change the position of the selected objects by a uniform amount. Note that the numbers you place in there are the amount to move, not the location to move to. For example, entering a Horz of 10 would move all select objects right by 10 pixels. Likewise,entering Vert of 10 would move all the selected object down by 10 pixels.Size:This section allows you to set the height and/or width of all the selected objects. Note that, unlike Position Change above, this refers to the actual size, not a change of size. Therefore, a Width of 50 would make all selected objects 50 pixels wide.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Objector</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1075</text>
</content>
<name></name>
<script></script>
</card>
card_22457.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Distribute: (w/ Abutt)If you choose Abut then the objects are placed so that they "butt" into each other in the manner that you have specified. The choice in popUps now refers the which item should remain still while the remainder butt into it. For example Rights would cause the right-most selected object to remain where it was and the others to butt against one-another from there.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Objector</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1074</text>
</content>
<name></name>
<script></script>
</card>
card_20678.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Distribute:Distribute allows you to spread a set of objects out evenly from one place to another. The "from" and "to" depend on your selections in the Horizontal and Vertical menus. For example, if you select Lefts from the Horizontal menu, then the left-most object selected will remain where it is, as will the right-most. The remainder of the selected objects will be distributed between them such that the distance from the left side of each to the next is the same. Likewise if you select Centers from the Horizontal menu the they would be distributed such that the distance between the center (left-right) of each to the next would be the same.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Objector</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1073</text>
</content>
<name></name>
<script></script>
</card>
card_20251.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Alignment:Select from the popup menus what part of the objects you want aligned. You may leave either (or both) blank to signify that you don't want any alignment in that direction. For example, selecting Left from the Horizontal menu alone would cause the left-sides of all the selected objects to be aligned. If you also selected Bottom from the Verticalmenu then the bottom-left corner of all the selected objects would be aligned.If you choose To Grid, then the objects will be aligned to the nearest grid line, instead of to each other. For example, if you selected both Left and Bottom from the alignment menus, and selected To Grid, then the bottom-left corner would be aligned to the nearest grid.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1072</text>
</content>
<name></name>
<script></script>
</card>
card_17687.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Objector is a powerful alignment tool which can manipulate any and all of the items in the dialog you are creating. With it you can align, distribute move or size a group of dialog items — in one easy step.To use it, simply click on the objector button or double-click on a group of items. A dialog appears with a list of all the dialog items on the left and a number of areas on the right.First select the items which you want to manipulate (don't forget this step!) If you had a previous selection or if you just double-clicked on a selection, Objector automatically selects items appropriately. Note: If you plan to align object to each other, be sure and select the one you don't want moved first.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1071</text>
</content>
<name></name>
<script></script>
</card>
card_32916.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The Export button allows you to install your hard work into another stack. This installation includes all the resources needed by the dialog and may include a button whose script contains an invocation of Dialoger with the necessary parameters to display the dialog as it is represented on the card.If you choose to have a button created, it will be placed on the clipboard from which it may be pasted onto the card of your choice in the target stack. If you have created a hit handler script in the card script, this too will be included with the button and installed in th stack script the first time it is clicked.Note: Like Show, this button does not re-Create the dialog. Therefore, if any changes have been made to the dialog itself, it should be recreated first.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Export</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1067</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_32697.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Changes that require making dialog again include:- position of items- size of items- addition of items- deletion of items- re-ordering of items- title of checkbox, radio button or push button- text in an editable or static text itemChanges that do not require making the dialog again:- text of userPop, userList- font & size of userList</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Show</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1066</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_32334.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The Show button allows you to quickly preview what the dialog will actually look like. It invokes Dialoger with the necessary parameters to display the dialog as it is represented on the card.Note: This button does not recreate the dialog. Therefore, any changes in the dialog itself (such as the position of the items) will not be reflected unless it has been recreated using the Create button above. When Dialog Maker believes that the card and the dialog are out of synch, it will give you the option of re-Creating the dialog first.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Show</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1065</text>
</content>
<name></name>
<script></script>
</card>
card_35151.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 3528end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Create</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Note: While a dialog’s window type and use are set separately, they are closely related and should be consistent. For instance, a floating palette should have a window type of Palette and a use of floating. A modal dialog shown in a palette windoid would be terribly confusing to the user and a crime against the Human Interface Guidelines! In general, a dialog’s window type and use should match up like this: Modal Modal Modal Modeless Float Orphan Orphan OrphanNevertheless, the choice and its incumbant responsibility is left up to you.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/27/90</text>
</content>
<name></name>
<script></script>
</card>
card_45176.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The Options button allows you to set various attributes of the dialog as a whole. You may set the way in which the dialog is being used (i.e. Modal, Modeless, Orphan, Float), the location at which the dialog is displayed, and the name of the hit handler to be used. If a hit handler is specified, a sample on will be created automatically in the card's script. This handler is used when Showing the dialog within Dialog Maker and is included in Exported buttons as well so it an ideal way to develop fully function interactive dialogs entirely within Dialog Maker.Other features such as the changing the default item, the cancel item and specifying a list which is to be key scrolled are also accessable from here.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_32157.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The dialog name serves as both the resource name for the DLOG resource and the title (in the case of dialogs with title bars). The popup menu allows you to select the dialog window type. (The titled + choice refers to the presence of a Go Away box).The checkbox Include Card Pic allows you to easily incorporate any graphics you have created on the card as a picture item. When checked, the card graphic will be transformed into a PICT resource and included in the list. Note: if the total area of the card graphic covers some other items, you will probably need to take the extra stepof transforming the pieces into PICTs first (using PICT Maker) and then laying them out so they don't overlap.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Create</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1064</text>
</content>
<name></name>
<script></script>
</card>
card_31588.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>> Radio Buttons are grouped according to their appearance in the list. All radio buttons which appear consecutively in the list will be grouped together such that only one may be selected at a time. If you want two separate groups of radio buttons, make sure they are split by some other type of item in the list - otherwise they will be consideredone large group.> Stacking order - when two item overlap, the item which receives the "hit" is the one which appears first on the list. Therefore, if you have, for example, userBox areas surrounding a group of radio buttons, the box must be listed after the radio buttons or they will never get the click which would select them.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Create</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1063</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_41000.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The Create button transforms the HyperCard objects into a real dialog (ie the necessary DLOG and DITL resources).When clicked, you will be presented with a list of all dialog items which will be included in the new dialog with a place to enter or change the name of the dialog itself. In addition, two buttons labeled Up and Down are provided so you can change the order in which the items are listed - and hence the order in which they appear in the DITL. This order is important for a variety of reasons:> Tab order. The tab key will move from the first editable text item in the dialog item list to the last. Normally, this should correspond to the upper-left-most item to the bottom-right-most item.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Create</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1062</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_30918.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The Import button allows you to import an existing dialog into HyperCard for editing. When clicked, you will be presented with a list of dialogs from which to pick. This list is composed of all the dialogs in this stack. To select a dialog from another stack, click on the Open… button and select the desired stack.The items in the dialog will be converted into card objects (buttons and fields) and placed in the correct positions on the card. (If the card already contains any card objects , you will be given the opportunity to either create a new card or to delete the existing objects.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1061</text>
</content>
<name></name>
<script></script>
</card>
card_51194.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Like pictures, boxes may also be split into a grid of buttons. Since they have no graphic image, they are most often placed over* another graphic (most likely a picture) to make the image come alive! Similar to using picture buttons, this capability is provided so that a portion of a picture may be divided into buttons.To access this capability, click on "Receives “Hits”…" in the item specifications dialog. Another dialog is presented which allows you to determine how many buttons the box should be split into. Notice that only one selection logics is supported: push button logic. This is due to limitations of the Dialog Manager. If you need Radio Button Logic, use a picture button instead.Note: Actually, the box must appear before the graphic in the item list or it will never "see" any clicks upon it.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_29054.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a box for the dialog box that you are designing. While you have great control over how the box will be displayed in the dialog (pen pattern, fill pattern, etc.…), these adjustments will not be readily apparent until you Show the actual dialog — HyperCard is incapable of displaying such niceties.Double-click on item to edit it; use Position button to precisely position the item. Like the various patterns and modes, the title will not appear until you Show the dialog.If you are using Dialog Maker to design dialogs which will not be displayed by dialoger, you should use these items to represent the "user areas" in the dialogs.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_30504.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new list item for the dialog box that you are designing. If you enter in the correct contents for the list, the Install button will be able to generate the proper script for creating the dialog.To change the contents of a list, double-click on it. The Text Style button allows you to change the font and size of the text in which the list will appear. Alignment, styles and textheight do not apply. Changes to these will only may the card look different that the dialog.If you are using Dialog Maker to design dialogs which will not be displayed by dialoger, do not use these items since they are an invention of Dialoger and won't have meaning.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>userList Tool</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1060</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_30287.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new popup menu item for the dialog box that you are designing. If you enter in the correct contents for the popup, the Install button will be able to generate the proper script for creating the dialog.To change the contents of a popup, double-click on it.PopUps may only be in Chicago 12 point.If you are using Dialog Maker to design dialogs which will not be displayed by dialoger, you cannot use these items since they are an invention of Dialoger and have no meaning elsewhere.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>userPop Tool</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1059</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_44639.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Progress Pict — this control is used for information purposes only; it cannot be set by the user. It simply moves the specified picture to indicate the degree to which an operation has been completed. It can accomodate any range of integer values but the most convenient is usually 1 to 100. This technique is often used with an orphan dialog where the value of the control is set periodically to indicate the progress of an operation. The dialog is then dismissed when the operation is completed.The progress pict may be oriented either horizonally or vertically. It will be offset from either the left side or bottom accordingly. The picture's name or id must be specified as the title.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_37349.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Progress Box — this control is used for information purposes only; it cannot be set by the user. It simply fills an empty box with a pattern to indicate the degree to which an operation has been completed. It can accomodate any range of integer values but the most convenient is usually 1 to 100. This technique is often used with an orphan dialog where the value of the control is set periodically to indicate the progress of an operation. The dialog is then dismissed when the operation is completed.The progress box may be oriented either horizonally or vertically. It will be filled from either the left side or bottom accordingly. If it is exactly square, a circle will be used instead where progress is indicated by filling an increasingly large slice. The pattern used is gray unless the title of the control is exactly one of these alternative fill pattern names: (Black, dkGray, Gray, ltGray, White.)</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_35606.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Scrollbar — while the buttons mentioned above have only two values, scrollbars are more flexible. They can accomodate a full range of integer values (ie 1-2-3 but not 1.5). This means that a particular scrollbar might represent a number between 1 and 100 — or perhaps between 97 and 423. However, since custom controls provide no automatic value-changing services, you will need to use a hit handler to manage the scrollbar. This is not a trivial undertaking… good luck!Note: since the thumb of the scrollbar represents the actual value, it may occupy only locations which represent an integer. This means, for example, that a scrollbar whose min is 1 and max is 3 will only have three possible locations for the thumb (far left, middle, far right). Dragging the thumb anywhere else will cause it to jump to the appropriate place.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_48711.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Checkbox — like the Radio Button above, this version of a checkbox uses the dialog's default font. The value of a checkbox is 0 when unhilited and 1 when hilted. Accordingly the min. and max. should be set to 0 and 1 respectively. Since custom controls provide no automatic value-changing services, you will need to use a hit handler to manage the hiliting of each button.Three-way Checkbox — This control is the same as the one above except that instead of only two states (1=true / 0=false), it also supports a third (2=maybe). This is handy in situations where the initial condition of the button is indeterminate. Since custom controls provide no automatic value-changing services, you will need to use a hit handler to manage the hiliting of each button. (Usually by cycling through the three possible values).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_14558.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Radio Button — like the Push Button above, this version of a radio button uses the dialog's default font. The value of a Radio Button is 0 when unhilited and 1 when hilted. Accordingly the min. and max. should be set to 0 and 1 respectively. Since custom controls provide no automatic value-changing services, you will need to use a hit handler to manage the hiliting of each button in a group.Three-way Radio Button — This control is the same as the one above except that instead of only two states (1=true / 0=false), it also supports a third (2=maybe). This is handy in situations where the initial condition of the button is indeterminate. Since custom controls provide no automatic value-changing services, you will need to use a hit handler to manage the hiliting of each button in a group.Note: The maybe state should only be used as an initial value, not as a result of the item having been clicked.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_37397.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new custom control for the dialog box that you are designing. You may choose either one of the built-in control types or any CDEF which has been installed in the Home Stack. You will also be asked for a title of the control, its value and the range of values that are allowed. The apperance and effect of the control in the actual dialog depends on its type. On the card, however, it simply appears as a box with its title. The types included in the Dialog Maker stack are:Push Button — identical in operation to the conventional push button item, this control differs only in its appearance. Rather than always appearing in Chicago font, it uses the dialog's default font (which may be set using the Font command). The value of a Push Button is 0 except while it is depressed — when its one. Accordingly the min. and max. should be set to 0 and 1 respectively.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_23106.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Pictures may also be split into a grid of buttons. While perhaps less than inspiring for a picture of a pizza, this technique can greatly increase your flexibility in design. For example, remember the New/Delete/Items buttons on the Index window? These were picture buttons. Coupled with the ability to instantly create a picture out of card art, this technique allows almost any image to become an active part of the dialog.To access this capability, click on "Receives “Hits”…" in the item specifications dialog. Another dialog is presented which allows you to determine how many buttons the picture should be split into. Also, two selection logics are supported: 1) push button logic (button does not remain selected after clicking on it), and 2) radio button logic (the button remains selected).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_28542.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new picture item for the dialog box that you are designing. You will be presented with a list composed of all the PICTs in this stack. To select a PICT from another stack, click on the Open… button and then select the stack. Once you have selected the desired PICT (its name and ID appear below the list), click OK. The PICT will be copied into this stack if necessary and the new picture item created. You may also turn a piece of the card into a new picture using the dialog's New button or delete an existing one using the Delete buttonWhile you may alter the size of the PICT, be aware that doing so will cause the image to be distorted.Normally, picture items appear only as white boxes. To see the actual PICT displayed, simply click on it. </text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Picture Tool</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1054</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_28293.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new icon item for the dialog box that you are designing. You will be presented with a list of icons from which to pick. This list is composed of all the icons in this stack. Once you have selected the desired icon (its name and ID appear below the list), click OK. The new icon item created. To select an icon from another stack, click on the Open… button and then select the stack. The icons in that stack will now appear in the list. Once an icon has been chosen, it will be copied into the Dialog Maker stack.You may also turn a piece of the card into an icon using the dialog's New button or delete an existing icon using the delete button.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Icon Tool</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1053</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_36467.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This tool had been used to create a special kind of user item which allowed styled text to be displayed in a dialog.The current version of Dialoger does not use this tool as the static text item has been enhanced to accomodate these capabilities.So, rather than using this, click on the static text tool, and then use the Text button to specify the text styles you want.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_26618.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Similar to HyperCard, Dialoger supports various styles of static text items. These are discussed below:Plain is a normal static text item. It uses the facilities built into the Dialog Manger and is the most straight-forward. It does have a limitation: the text always appears in the default font for the dialog — normally Chicago. Opaque and Scrolling support text of any style to be entered. Using the Text button, you may control the font, size, style — even alignment and lineheight of the text entered into the item. While more flexible than Plain text, there is a slight penalty in performance and memory for these features. Also, since these styles are an invention of Dialoger, they do not support the replacement text feature of Plain static text (ie ^0, …, ^3).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_27613.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new static text area forthe dialog box that you are designing. You will be asked for the text which will appear when the dialog is first presented to the user.Notice that the right side of the item is expanded automatically when you alter the text it contains — if you don't want this, simply alter the item’s dimensions yourself (if the item’s width has been altered by you, Dialog Maker will no longer adjust it itself).In addition to the built-in static text facilities of the Dialog Manager, Dialoger also supports other styles of static text items. While not as extensive as HyperCard's they offer a valuable addition to the Dialog Manager's own.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1050</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_12543.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Plain is a normal editable text item. It uses the facilities built into the Dialog Manger and is the most straight-forward. It does have a limitation: the text always appears in the default font for the dialog — normally Chicago. Rectangle and Scrolling support text of any style to be entered. Using the Text button, you may control the font, size, style — even alignment and lineheight of the text entered into the item. While more flexible than Plain text, there is a slight penalty in performance and memory for these features.Protected masks entry into the text item by displaying symbols rather than actual characters as they are typed. This feature is handy for requesting passwords or other secure information. </text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Edit Text Tool</text>
</content>
<name></name>
<script></script>
</card>
card_27073.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new editable text area for the dialog box that you are designing. You will be asked for the text which will appear as a default when the dialog is first presented to the user. You may leave this blank if desired.If you want to change the height of the editable text area,you must be careful. The text will "jump" when edited unless you set the height to 6 + (16 * #of lines) (ie 22 = 1 line high, 38 = 2 lines high, 54 = 3 lines high, etc.). A newly created editable text area is the correct height for 1 line.In addition to the built-in editable text facilities of the Dialog Manager, Dialoger also supports other styles of editable text items. While not as extensive as HyperCard's they offer a valuable addition to the Dialog Manager's own.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1048</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_26638.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new checkbox for the dialog box that you are designing. You will be asked for the name of the button which will appear as the title of the button.Notice that the right side of the button is expanded automatically when you change the button's name — if you don't want this, simply alter the button's dimensions yourself (if the buttons width has been altered by you, Dialog Maker will no longer adjust it itself).</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Checkbox Tool</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1047</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_26190.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new radio button for the dialog box that you are designing. You will be asked for the name of the button to appear as the title.Notice that the right side of the button is expanded automatically when you change the button's name — if you don't want this, simply alter the button's dimensions yourself (if the buttons width has been altered by you, Dialog Maker will no longer automatically adjust it).Radio buttons are grouped together such that only one may be selected at a time. Since Dialoger groups radio buttons that are next to each other in the item list, create all the radio buttons in a group at once. And, by extension, place some other type of item between to separate groups of radio buttons.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Radio Button Tool</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1045</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_25939.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>This button allows you to create a new push button for the dialog box that you are designing. You will be asked for the name of the button which will appear as a title in the middle of the button.Most dialogs should have an OK button as the first item in the dialog and a Cancel button as the second. In fact, if you don't, you will be reminded of this convention. The reason behind this comes from the Dialog Manager which intreprets the Return key as a click on item 1 and a Command-Period as a click on item 2. While these assumptions may be changed, it is more straightforward to simply play by the rules.Note: HyperCard displays push buttons in a slightly different manner than they appear in a dialog. This is normal.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Push Button Tool</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1044</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_18614.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>To select an object — click on itTo add another object to the selection — shift-click on itTo remove an object from the selection — shift-click on itTo move object(s) — drag themTo resize object(s) — drag one of their cornersTo undo either of above while dragging — drag to menubarTo align (etc.…) group of objects — double-click on selectionTo edit an object — double-click on objectTo nudge object(s) while selected — use Arrow keysTo align selected objects — use Shift + Arrow keysTo resize selected objects — use Option + Arrow keysTo align by resizing — use Shift + Option + Arrow keysTo delete object(s) while selected — use Delete key</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Objects</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1042</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/13/90</text>
</content>
<name></name>
<script></script>
</card>
card_18306.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Wait a minute — aren't we still using the browse tool?Yes, unlike "normal" HyperCard, which makes you switch back and forth between the "button tool" and the "field tool" to manipulate objects (buttons and fields), Dialog Maker makes it easy to manipulate them together. In most cases, working with the browse tool is just like working with the button (or field) tool — only better.You can select multiple objects, move them together, resize them together, even delete them together using the techniques summarized on the next card. Especially handy is the ability to restrict virtually all these activities to an invisible grid. To do so, simply depress the Command Key while dragging or resizing. And, if you want to see the objects move themselves (rather than their outlines) hold down the Caps Lock Key.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1041</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_40448.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>For now, let's skip over Objector and move directly to the top portion of the palette to discuss the creation of the various dialog items. Each of these tools represents a different kind of dialog item. To add an item to the dialog you are designing, click on the appropriate tool. A new item will be created and a specifications dialog presented. With this specifications dialog you can control most aspects of an item's appearance and operation. (You can get this dialog at any time by double-clicking on the item).Once created, the item may be dragged into place. So too may it be resized in the standard HuperCard way — by dragging any corner. By the way, you will have already figured out that each card comes with a box already in place. This box represents the whole dialog so item should be positioned within it. Like individual items, it may be dragged, resized and even double-clicked.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_46777.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>New — creates a new card on which a new dialog may be created from scratch (or an existing one imported).Delete — deletes the selected dialog from the Dialog Maker stack (and its card as well). A list of all the resources used by the dialog is presented. Only those resources which are selected will be deleted so those shared by more than one dialog (eg PICTs) may be spared from their fate by making sure they are not selected. Note: for technical reasons, the deletion does not take place immediately, but rather, when you next leave the stack — for any reason.Items — expands the dialog to display a list of the items in the dialog. This list can serve as a handy reference while working on a dialog (particularly its hit handler).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/18/90</text>
</content>
<name></name>
<script></script>
</card>
card_50384.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on closeFieldput the date into bg fld "date"end closeField</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Index</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<content>
<layer>card</layer>
<id>2</id>
<text>Next, let's look at the Index tool. This tool displays an index or table of contents for the Dialog Maker stack. Simply click on a dialog's name to see its card. (Since this list contains all the dialogs contained in the resource fork of the stack, it may also include dialogs which do not have any card. If so, clicking on that line will obviously not move to the non-existent card.)Below the list of dialogs there are three buttons: New, Delete and Items. These are discussed individually next.</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text></text>
</content>
<name></name>
<script></script>
</card>
card_33266.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>In examining the tool palette and the wealth of capability it represents, let's start from the bottom and work our way up. In particular, let's start with the help button.This tool displays a separate window with a complete set of help information on the use of each tool in the palette as well as a quick reference to the various commands available for use in Dialoger and dChanger.In the window that is displayed, a replica of the tool palette is presented. Simply click any tool on this replica to see information about its meaning and use. Once a tool is selected, the popup menu at the bottom contains all the possible commands appropriate for that dialog item. Choose one of these commands to see its description and syntax. (For commands to the dilaog as a whole, first choose any one of: Import, Create, Show, Export).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_27844.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Tools — Lurking behind this quiet button is the bulk of the power of Dialog Maker. This button displays the special tool palette used in Dialog Maker. This palette is split into three parts. The top part is a set of a dozen tools which allow you to create dialog items on the card. Clicking on one will make the indicated dialog item. The middle part consists of operations on the Dialog as a whole. These tools allow you import existing dialogs, create real dialog resources, show the actual dialog and finally to export the completed dialog to another stack.The final part access three additional windows: Helper — guess what, Objector — a sopohisticated alignment dialog, and Index — a table of contents for dialogs in the stack.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/18/90</text>
</content>
<name></name>
<script></script>
</card>
card_40370.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on closeFieldput the date into bg fld "date"end closeField</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text></text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<content>
<layer>card</layer>
<id>1</id>
<text>The About Box — This button will display a small window of information about the dialog on the card. Every example dialog has an extensive discussion of its purpose and use available in this dialog. For dialogs which you create, this may be used as a general-purpose notepad.Dialog Name — Unsurprisingly, this is the name of the dialog. For dialogs which have title bars, this also corresponds to the title of the window.Navigation Arrows — A familiar sight in HyperCard, these arrows allow you to go to the previous or next cards — or to return from a digression. Going Places — These buttons along the bottom allow you to go home or to this help stack quickly.</text>
</content>
<name></name>
<script></script>
</card>
card_47294.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUphide cd picthide cd btn id 1show cd btn id 2end mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>226</top>
<right>503</right>
<bottom>246</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Dialog Maker</name>
<script>on mouseUpshow cd btn id 1show cd picthide meend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>While these two examples (and their siblings in the Dialog Maker stack) provide much needed relief from HyperCard's more vexing limitations, they just scratch the surface of what is possible with Dialoger Professional.Using the Dialog Maker stack, you can create dialogs of any size and description which are capable of performing all sorts of amazing feats. To do this, of course, you will need to become familiar with the operation of the stack So, let's take a closer look at a typical card. A click on the button at right will revel a picture of the card in the Dialog Maker stack which houses the Ask2 dialog.Now we can discuss each of the elements in detail.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script>on closeCardsend mouseUp to cd btn id 1end closeCard</script>
</card>
card_42674.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpGet Stop("Should I alert the media before proceeding?", "Yes", "No", "Cancel")if it is "No" then answer "Discretion is often the better part of valor."else if it is "Yes" then answer "Gotta love that limelight"else if it is "Cancel" then answer "Chicken"end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Examples</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Alert — This dialog is an extension of HyperCard's own Answer dialog. Instead of allowing only one line of text, this function allows up to four. In addition, one of the three standard alert icons (Stop, Caution, Note) may be displayed in the dialog. When you export this example to another stack, three HyperTalk functions Stop, Caution and Note will be installed in the stack script. They're only difference is the icon they show. Each has identical syntax: Note(«Message», «Button1», «Button2», «Button3»)and returns the label of the button clicked by the user.For example, using it to warn of an ugly situation might look like this: Get Stop("Are you sure?", "Yes", "No", "Cancel")</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/18/90</text>
</content>
<name></name>
<script></script>
</card>
card_42316.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpglobal oldFind,oldReplaceGet Ask2("Find:", "Replace with:", oldFind, oldReplace)if it is not empty thenput line 1 of it into oldFindput line 2 of it into oldReplaceanswer "Replace all occurances of"&&oldFind¬&&"with"&&oldReplace&"."end ifend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Maker</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Examples</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Ask2 — This dialog is an extension of HyperCard's own Ask dialog. Instead of allowing only one place to enter text, this function allows two. When you export this example to another stack, a HyperTalk function Ask2 will be installed in the stack script which has the following syntax: Ask2(«Prompt1», «Prompt2», «Default1», «Default2»)and returns whatever was typed in by the user in the form «Answer1» & return & «Answer2».For example, using it to illicit find & replace info might look like this: Get Ask2("Find:", "Replace with:", oldFind, oldReplace)</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/18/90</text>
</content>
<name></name>
<script></script>
</card>
card_2441.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Dialog Maker is a complete environment for the creation of dialogs. With it, you lay out buttons and fields on a card as representatives of the items desired in the dialog. The card is then used to create a real dialog — complete with DLOGs, DITLs, CNTLs and other impressive acronyms. Once created, the dialog is ready to go. It can be prototyped (ie shown) where it is or exported to another stack for further refinement. (While Dialog Maker automates the scripting process as much as possible, sophisticated dialogs do require you to roll-up your sleaves a bit ).Since Dialog Maker is organized around the concept of one card, one Dialog, you can collect your dialog designs in this one place and reuse them as needed. To help get you started, your Dialog Maker stack already contains a number of basic dialogs coupled with handy scripts. Some of these are described on the following pages.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1040</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/18/90</text>
</content>
<name></name>
<script></script>
</card>
card_54027.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 61137end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>The Answer Is…</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>There is a complication when scrolling editable text is involved. Since the user may type RETURN into those fields, they could really screw up the organization of dResult. Fortunately, Dialoger watched out for this problem. When it occurs, the contents of the editable text item is “scrunched” down into one line by changing the Return characters to a more innocuous one. This change ensures that the contents of the editable text item will stay put in its alloted line in dResult. To restore the text back to its pristine state (ie with its Returns), a simple XFCN called Unscrunch has been provided. It undoes — fittingly enough — the effects of Dialoger’s scrunch. So, if item 9 in a dialog was a scrolling editable text area, we could use a statement like “put UnScrunch(line 9 of dResult) into theEnteredText”. </text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/27/90</text>
</content>
<name></name>
<script></script>
</card>
card_6003.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput "Small" & return &¬"Medium" & return &¬"Large" & return &¬"Ex Large" into PopUp1put "Anchovies" & return &¬"Hamburger" & return &¬"Mushrooms" & return &¬"Onions" & return &¬"Pepperoni" & return &¬"Peppers" & return &¬"Sausage" into List1put Dialoger("Example"¬, ""¬ -- Replacement text, ""¬ --Button "Motto…", "true"¬ --Radio Button "Deep Dish", ""¬ --Radio Button "Thin’n crispy", ""¬ --Checkbox "Home Delivery", "Any Name Goes Here"¬ --Editable Text "", ""¬ --Icon "20086", ""¬ --Card Picture, "userList 3335" & return & List1¬ --List, "userPop 1, 15" & return & PopUp1¬ --PopUp, "StyledText New York,18,BU"& return &"Peter’s Pizza Palace"¬ --Text "Peter’s Pizza Palace", "userBox" &return &" Style "¬ --Box (Black pen, None fill) " Style ", "userBox Gray"¬ --Box (Gray pen, None fill)) into dResultput dResult into cd fld "resultLines"lock screenshow cd fld "box"show cd fld "items"show cd fld "resultLines"unlock screenwait until the mouse is downlock screenhide cd fld "box"hide cd fld "items"hide cd fld "resultLines"unlock screenend mouseUp</script>
</part>
<part>
<id>4</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>26</left>
<top>113</top>
<right>343</right>
<bottom>302</bottom>
</rect>
<style>rectangle</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>box</name>
<script></script>
</part>
<part>
<id>2</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>214</left>
<top>115</top>
<right>341</right>
<bottom>300</bottom>
</rect>
<style>transparent</style>
<autoSelect> <false /> </autoSelect>
<showLines> <true /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>plain</textStyle>
<textHeight>13</textHeight>
<name>resultLines</name>
<script></script>
</part>
<part>
<id>3</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>28</left>
<top>115</top>
<right>215</right>
<bottom>300</bottom>
</rect>
<style>transparent</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>right</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>bold</textStyle>
<textHeight>13</textHeight>
<name>Items</name>
<script></script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>The Answer Is…</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Since Dialoger is an XFCN, it returns something for all your efforts. Specifically, it returns a description of each item in the dialog as of the moment the dialog was dismissed. These descriptions are organized by placing each item on its own line; item one gets line 1, item 2 gets line 2… What does this "description" look like for each item? Well, it varies according to the type of item:Radio Buttons & Checkboxes — either "true" or "false"Push Buttons — empty unless button dismissed the dialog - in which case its title is returnedIcon & Pictures — empty except picture buttons which return the part selectedCustom Controls — their valueEditable Text — the text that was entered thereuserPop — the text of the item last selecteduserList — a comma separated list of selected line numbers</text>
<text>There are three optional modifiers which provide complete control over what a userBox box looks like. The first allows you to specify a pen pattern, the second allows you to specify a fill pattern, and the third a transfer mode.In our example, we want the line above the push buttons to be dotted. We can accomplish this by using a gray pattern for the pen: "userBox gray"Just for the fun of it, let's see what happens if we ask for a gray fill for our other box (ie "userBox black, gray")The box may also have a title which you provide in the second line of the parameter. This is especially useful for visually grouping radio buttons together — like our group.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Modifiers</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1038</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_16647.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The final kind of Fancy Item that Dialoger currently supports is a box. Just as it sounds, this is a box drawn around the perimeter of the item.If item n is to be a Box then parameter n should be the word "userBox" (but the parameter may be omitted entirely, if you wish, since all user items default to userBoxes unless otherwise initialized). In our example, we have two userBoxes which have appeared all along. The first surrounds the radio buttons and the second looks like a line since it is only 1 pixel thick.We are going to use some of the modifiers available for userBoxes to change these.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Boxes</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1037</text>
</content>
<name></name>
<script></script>
</card>
card_45918.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Users of earlier versions of Dialoger will notice the absence of the userText command. Fear not! It is still supported and may be sent to a user item (whereas the styledText command is sent to text items.) However such users should note carefully the third modifier to the StyledText command as it reflects a change which also applies to the userText command. In brief, the third modifier to the userText command no longer allows you to draw a box around the text item. Instead, it is dedicated to a set of codes which define the styling of the text. This change allows far greater flexibility over the styling of the text item.If you need a box drawn around your userText item, simply modify the dialog to include a userBox item around the text. Sorry about the inconvenience.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>userText</text>
</content>
<name></name>
<script></script>
</card>
card_46112.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on closeFieldput the date into bg fld "date"end closeField</script>
</part>
<content>
<layer>background</layer>
<id>6</id>
<text>While you have undoubtedly already fingured out that the first two modifiers supply the font and fontsize of the text, the third one is far more cryptic. Essentially, it is a set of one character codes which communicate the various styling options to Dialoger. They are summarized below: B = Bold I = Italic U = Underline O = Outlined S = Shadowed W = Word Wrap N = No Word Wrap ! = Scrollbar . = No Scrollbar</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>StyledText</text>
</content>
<content>
<layer>card</layer>
<id>3</id>
<text>1 = Single Spaced2 = Double Spaced3 = Triple Spaced5 = 1-1/2 Spaced7 = 2-1/2 SpacedL = Left AlignedM = Middle AlignedR = Right Aligned</text>
</content>
<name></name>
<script></script>
</card>
card_16096.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Normally, the text items which appear in a dialog are all confined to be the same font, size and style. Naturally, Dialoger provides a way to overcome this limitation. A special command transforms normal text items into ones which can have every aspect of their appearance and operation individually controlled — they can even have a scrollbar. This command is described here since it takes the same form as commands creating other fancy items. Remember, however, that it is given to a text item rather than a user item. The command packs information about the font, size and all other characteristics of the text item into three modifiers. For example: "StyledText New York,18,UB"causes the text "Peter's Pizza Palace" to appear in New York font at 18 point size underlined and bold.</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>StyledText</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1035</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<name></name>
<script></script>
</card>
card_47500.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput Dialoger("Example", "9◊PictButton 3,2") into dResultend mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>251</top>
<right>503</right>
<bottom>273</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Radio</name>
<script>--Sample script for invoking "A Pal"--Created on Wednesday, March 14, 1990on mouseUpglobal dResultput return into CR-- --------------------------------- Items in Dialog: "A Pal"-- --------------------------------- 1 ◊ Picture "26862"-- -------------------------------put Dialoger("A Pal" & CR &¬"Float"¬, "1◊PictButton 3,1,Radio"¬) into dResultif word 1 of dResult is "Error:" then answer dResultend mouseUp</script>
</part>
<part>
<id>3</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>212</top>
<right>503</right>
<bottom>234</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Push</name>
<script>--Sample script for invoking "A Pal"--Created on Wednesday, March 14, 1990on mouseUpglobal dResultput return into CR-- --------------------------------- Items in Dialog: "A Pal"-- --------------------------------- 1 ◊ Picture "26862"-- -------------------------------put Dialoger("A Pal" & CR &¬"Float"¬, "1◊PictButton 3,1,Push"¬) into dResultif word 1 of dResult is "Error:" then answer dResultend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Picture Buttons</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>This command has three modfiers. The first two allow you to split the picture into a grid of buttons. They are «Across» and «Down». For example (item 9 is the pizza): get Dialoger("Example","9◊PictButton 3,2")would split the pizza into six buttons; three across and two down. If «across» and «down» are omitted, it is assumed that the picture is to be a single button.The third modifier is «logic». Dialoger supports two selection logics among the buttons of a single picture. The default "Push" is akin to a set of push buttons — any one may be selected — but only monentarily. "Radio" on the other hand, acts like a group of radio buttons. Only one button may be selected at a time and that part remains selected. The HyperCard tool palette behaves this way. </text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/19/90</text>
</content>
<name></name>
<script></script>
</card>
card_9890.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpanswer "This was just a test…"end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Picture Buttons</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>HyperCard has spawned a new kind of interface element —called a picture button. Essentially, this any kind of button which, instead of being — say a push button — looks like a picture of something. This design gives you complete control over the appearance of the button. Of course, Dialoger supports this innovation. You can specify that a picture should respond to a click just like a button. In fact, you can split a picture into a grid of buttons — any one of which can be selected. A perfect example of this is a palette of tools where the whole palette is split into a grid of individual tools. Now you have a set of buttons — each part of a picture — all for the price of one picture.Dialoger transforms a normal picture into this wonder of modern technology with the PictButton command.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/14/90</text>
</content>
<name></name>
<script></script>
</card>
card_44510.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 13909end mouseUp</script>
</part>
<part>
<id>3</id>
<type>field</type>
<visible> <true /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>143</left>
<top>44</top>
<right>267</right>
<bottom>307</bottom>
</rect>
<style>transparent</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>New York</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>15</textHeight>
<name>Wisdom</name>
<script>on closeFieldput the date into bg fld "date"end closeField</script>
</part>
<part>
<id>4</id>
<type>field</type>
<visible> <true /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>274</left>
<top>44</top>
<right>392</right>
<bottom>307</bottom>
</rect>
<style>transparent</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>New York</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>15</textHeight>
<name>Wisdom</name>
<script>on closeFieldput the date into bg fld "date"end closeField</script>
</part>
<content>
<layer>background</layer>
<id>6</id>
<text>Meta - displays a text list similar to the default one but with enhancements modeled after the meta characters used in menu creations. These meta-characters allow you to individually style a list line, inactivate it, etc. A brief summary or valid meta characters appears below: When the one (or more) of these appear in the text of a list line, it is removed from the text and causes that line (only) to aquire the designated style. <B = Bold <O = Outlined <E = ExtendedFor a complete description of how these meta characters work, see the section on meta characters.</text>
<script>on mouseUpput resIDNameList("","ICON") into List1 -- IDs of all iconsput Dialoger("A List","3◊userList Labeledicons"&return&List1) into dResultend mouseUp</script>
</part>
<part>
<id>4</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>114</top>
<right>503</right>
<bottom>134</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>A List</name>
<script>on mouseUpput resIDList("","ICON") into List1 -- IDs of all picturesput Dialoger("A List", "3◊userList icons"&return&List1) into dResultend mouseUp</script>
</part>
<part>
<id>5</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>139</top>
<right>503</right>
<bottom>155</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>ResIDList</name>
<script>on mouseUppush cdgo to card id 34558end mouseUp</script>
</part>
<part>
<id>6</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>261</top>
<right>503</right>
<bottom>281</bottom>
</rect>
<style>roundrect</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>A List</name>
<script>on mouseUpput resIDList("","PICT") into List1 -- IDs of all picturesput Dialoger("A List","3◊userList picts"&return&List1) into dResultend mouseUp</script>
</part>
<part>
<id>7</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>217</top>
<right>503</right>
<bottom>233</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>ResIDNameList</name>
<script>on mouseUppush cdgo to card id 45375end mouseUp</script>
</part>
<part>
<id>8</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>287</top>
<right>503</right>
<bottom>303</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>ResIDList</name>
<script>on mouseUppush cdgo to card id 34558end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Special Lists</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>It is doubtful that you will want to run out and write a List DEFinition (LDEF). Luckily, the Dialoger stack includes some LDEFs which are ready to go. These include:Icons - displays a two-dimensional list of icons. The text of the list should be the IDs of the icons to be displayed in the list. Where do you get this list of icon IDs? There is a XFCN called ResIDList which can do that for you.Named Icons - similar to the above except each icon has a lable below it — just like those in Finder. The text of this list should consist of «ID», «Label» for each line. Another XFCN called ResIDNameList might come in handy here.Picts - displays a list of pictures (PICT resources)— one at a time. The text of the list should be the IDs of the PICTs to be displayed in the list. ResIDList might help here too.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1034</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<name></name>
<script></script>
</card>
card_15496.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>In order to create a list item, Dialoger uses another part of the toolbox, the List Manager. This manager already knows how to display simple text lists like the ones you have already seen. It also allows you to "teach" it how to display other kinds of lists with a new kind of resource called a List DEFinition (LDEF). With the proper LDEF, for example, you can display a list of icons, or a list of pictures, or a list of anything else you wanted.Dialoger let's you take advantage of this powerful capability by allowing you to specify an LDEF other than the standard one to be used for the list. Simply supply the Name or ID of the LDEF resource you want used as the one and only modifier to "userList" (eg "userList icons").Note: Font and Size may not be changed for a custom LDEF.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1033</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_44020.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 18933end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>List Modifiers</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>The third modifier to the userList command has a split personality. Rather than defining a selection logic, it may instead be an item number. This item is to be considered “clicked” when a list line is double-clicked on. For example, try double-clicking on a list line in the example below: "userList Geneva,10,1" & return & List The "1" as a third modifier cause the double click to be interpreted as a click on item 1 — the OK button. The dialog is dismissed just as it would have been if you had clicked on the OK button yourself.Note: This «doubleclick item» does not have to be the OK button. It may be a button which alters the dialog without dismissing it — such interactive changes to the dialog are accomplished using dChanger which we disuss later.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<name></name>
<script></script>
</card>
card_21602.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>A userList may also accept a third modifier «Logic» which affects the logic it uses for selections (ie how selecting a line with affects previous selections). The options are:SingleSelection — only one line may be selected at a time. A new selection always deselects any previous one.ContiguousSelection — one or more items may be selected by dragging through the list. However, all previous selections are deselected with each click so only a single block of lines may be selected.AnySelection — any set of lines may be selected. This is the default. A command-click reverses the selection of the line and shift-click expands the selection through the line. NoSelection — no list lines may be selected at all. </text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1032</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<name></name>
<script></script>
</card>
card_43306.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Similarly, «Font Size» allows you to specify a font size other than 12 point. Since this is the second modifier, it must always be preceeded by a font name (and then a comma. Expanding once again on our example: "userList Geneva,10" & return & List would cause the list to be displayed in 10 point Geneva.Note: Dialoger will always adjust the bottom of the list to make sure a whole number of lines is displayed. This prevents the weird scrolling associated with partially displayed lines.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>List Modifiers</text>
</content>
<name></name>
<script></script>
</card>
card_15116.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>It is sometimes convenient to display a list in a different font and/or size than the default (Chicago 12 point). Happily, "userList" can accept two modifiers to alter these:«Font» allows you to specify a font in which you want the list to appear. Using the previous example: "userList Geneva" & return & List would cause the list to be displayed in the Geneva font. Another example would be: "userList Monaco" & return & List See the difference?</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1031</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<name></name>
<script></script>
</card>
card_15090.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>If item n is to be a List then the first line of parameter n must begin with "userList". Subsequent lines should contain the actual list lines. In our example, the tenth item of the DITL is a user item which we want to be a list of pizza toppings, so the tenth parameter could be: "userList" & return & "Anchovies" & return & "Ham…"A more convenient way to do this might be to put the lines of the List into a container (eg List1) and then make the parameter: "userPop" & return & List1That is all that is required to make a List!</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1030</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/7/90</text>
</content>
<name></name>
<script></script>
</card>
card_11678.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpif the cmdKey is downthen set lockText of me to not lockText of meelse set visible of me to not visible of meend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>6</id>
<text>«Title Item» is used when you want some other dialog item to act as the title for the popup. This title will be auto-matically inverted when the popup is clicked on.* Expanding once again on our example, "userPop 1, 15" & return & PopMenu would cause item number 15 (the static text "Size:") to be highlighted as a title whenever the popup was clicked.The word «FixedWidth» as the third modifier forces Dialoger to not fine tune the width of the item to match the menu that pops up. For example "userPop 1, 15, FixedWidth" & return & PopMenu would cause the item's appearance to not be adjusted.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<content>
<layer>card</layer>
<id>2</id>
<text>If you make the popup item itself the title item, the menu will drop below the item,— just like a menubar menu.</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Popup Modifiers</text>
</content>
<name></name>
<script></script>
</card>
card_13482.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>There are three modifiers which may be used with popup menus: «Initial Selection», «Title Item» and «FixedWidth».«Initial Selection» allows you to specify a menu choice which is to be pre-selected when the dialog appears. Using our example: "userPop 1" & return & PopUp1would automatically select "Small" (choice 1). Or, you may supply the text of the menu item instead. For example: "userPop medium" & return & Popup1would automatically select medium from the popup menu.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1029</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/8/90</text>
</content>
<name></name>
<script></script>
</card>
card_13108.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>If item n is to be a Popup Menu, then the first line of parameter n must begin with "userPop". Subsequent lines should contain the menu choices. In our example, the eleventh item of the DITL is a user item which you want to be a popup menu of pizza sizes. Therefore the eleventh parameter could be: "userPop" & return & "Small" & return & "Medium" & …A more convenient way to do this might be to put the lines of the PopUp into a container (eg PopUp1) and then make the parameter: "userPop" & return & PopUp1That is all that is required to make a Popup!</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1028</text>
</content>
<name></name>
<script></script>
</card>
card_13600.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 7899end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Modifiers</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Before a detailed discussion of each kind of Fancy Item, let's look at the general form of their parameters.If item n is to be a Fancy Item, then the first line of parameter n must begin with a label which describes the kind of Fancy Type it is. Popup menus, for example, are identified by "userPop", Lists by "userList" and Boxes by "userBox". Subsequent lines of the parameter are used to supply the contents of the Fancy Type; menu choices, list lines, etc.Note: Following the label on the first line of the parameter, there can be one or more modifiers (separated by commas)which provide you greater control over the appearance or behavior of the Fancy Item. These modifiers are optional but, if included, must appear in the correct order.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1027</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_12982.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Fancy Items, you remember, are things which the Dialog Manager doesn't know about — they are all lumped together in the DITL as "User Items". Dialoger, however, supports a powerful set of fancy items which includes: Popups, Lists, and Boxes.Notice that all the different items previously discussed had everything they need in the DITL resource. You only needed to supply information in the parameter if you wanted to change something. Well, since the Dialoger manager doesn't know about fancy items and since the DITL only holds information for the Dialog Manager, we're going to have to do a little more work for our fancy items: a parameter is always necessary. This is because at the very least we will need to tell Dialoger which kind of Fancy Item we want item n to be.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1026</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/7/90</text>
</content>
<name></name>
<script></script>
</card>
card_12588.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>If item n is a graphic item (ICON or PICTure), parameter n may be used to change its contents. It may also be left blank or even omitted entirely.Since graphic items exist as resources separate from the DITL which uses them, you may request that a different one be used in place of the one specified in the DITL. Simply supply either the Name or the ID of the resourcein the parameter. For example, if the fourth item in a DITL is an icon named "sm Arrow" and you want it to be the icon named "lg Arrow", simply use the name of the new icon as the fourth parameter. Likewise, you can change the PICT resource to be displayed as item n.You may not specify an ICON in a PICT's place or visa versa.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1025</text>
</content>
<name></name>
<script></script>
</card>
card_12185.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 10735end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Text</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>If item n is a text item, parameter n may be used to change its contents. It may also be left blank or even omitted entirely.If you want different text to appear than that which is in the DITL, you can supply it here as the parameter. For example, if the fourth item in a DITL is a static text item that contains "Select One:" and you want it to read "Select One or More:" when your dialog is displayed, simply use the new text as the fourth parameter. Careful — since the DITL also describes the size of the text item, it is possible to supply new text which will not all fit in the allotted space. If so, any excess will be truncated.Note: Substitution text can also change the contents of static text items. The choice is left to you.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1024</text>
</content>
<name></name>
<script></script>
</card>
card_11349.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 6902end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Buttons</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>If item n is a button, parameter n may be used to either change its name or set its value. It may also be left blank or even omitted entirely.You may change the name of a button by simply providing the new name as the parameter. For example, if the fourth item in a DITL is a push button named "Oldies" and you want it named "Latest" when your dialog is displayed, simply use "Latest" as the fourth parameter.Check boxes and radio buttons are always unchecked in the DITL resource. If you want one of them to be checked when the dialog is displayed, you must set its value by using "1" or "true" as the parameter. (Push buttons never remain "checked" so you cannot set their value). Remember: only one radio button in each group should be checked.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1023</text>
</content>
<name></name>
<script></script>
</card>
card_12023.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 52012end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>OK and Cancel</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Whoa! What about items 1 and 2? Don't they get they get the opportunity to have their initial value set? Yes.But first, let me digress. By a convention established by the Dialog Manager, item 1 should always be the "OK" button (though its name may differ), and item 2 should always be the "Cancel" button (though, likewise, its name may differ). In addition, pressing the Return (or Enter) key is interpreted just like a click on item 1. Pressing cmd-. is interpreted as a click on item 2. So it is important that these first two are what the Dialog Manager expects.About the only thing you might want to do to an OK or Cancel button is to change their name — or perhaps inactivate the OK button. The technique used to access these items is called explicit item number addressing. impressive name, huh! Both forms are used throughout. </text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1022</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_11209.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 8500end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Item Values</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Dialoger may take up to 16 parameters. We have already discussed what the first two are for which leaves us only numbers 3 through 16! Luckily, they may all be explained at once. In order to do so, however, I need to introduce a little shorthand: "n" stands for any number between 3 and 16, OK?One more thing. Remember that dialog items come in a list (the DITL resource)? Well each item in that list can be thought of as having a number which corresponds to its place in the list (ie the first item in the list is number one, the second is number two, etc.)Now we’re ready: parameter n is the initial value of dialog item n. What this initial value is and whether it is necessary or not depends on the kind of item n is.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1021</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/7/90</text>
</content>
<name></name>
<script></script>
</card>
card_10735.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Now we're ready to look at the second parameter of Dialoger... but first a word from our sponsor, the Dialog Manager: Since you often don't know what you'll want a text item to "say" until you're ready to display the dialog, it seems unfair that you are required to decide on the text when creating the DITL resource — long before you ever show the dialog. To alleviate this problem, the dialog manager allows you to use placeholders in the DITL which will be replaced with the proper text when the dialog is displayed. These placeholders are: ^0, ^1, ^2 and ^3.The second parameter allows you to provide the "real" text to substitute for any placeholders in the text items. Each line in the parameter replaces a different placeholder:line 1 replaces ^0, line 2 replaces ^1, line 3 replaces ^2, line 4 replaces ^3.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1020</text>
</content>
<name></name>
<script></script>
</card>
card_9273.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput Dialoger("Example") into dResultend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Our Example</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>By the way, I hope you liked that dialog box… We will be using it throughout this section to illustrate the various capabilities of Dialoger. While it may look a little boring now… just you wait… all those plain boxes are going to be transformed into popup menus, lists and other fun-filled items.While the text (like this stuff here) should give you a good idea of what additions are begin made to the script of the Example button, feel free to take a look as you go. (The easiest way is to hold down the command and the option key while clicking on the button). Also, experiment yourself by changing the script of the button and seeing the effect… OK, now back to work!</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1018</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/7/90</text>
</content>
<name></name>
<script></script>
</card>
card_10467.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>The first parameter must provide the name of the DLOG to be displayed. Optionally, it may also provide additional information about how to display the dialog as a whole. It does this in successive lines of the first parameter. These additional lines may alter such things as the font and size of the text items and the location of the dialog window. The exact form of these commands can be found in the Command Reference section but here are a some examples: get Dialoger("Example"&return&"Font Geneva") get Dialoger("Example"&return&"Font Geneva"& return&"Fontsize 10") get Dialoger("Example"&return&"Loc 100,40")</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1019</text>
</content>
<name></name>
<script></script>
</card>
card_10009.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput Dialoger("Example") into dResultend mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>246</top>
<right>503</right>
<bottom>262</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>The Answer Is…</name>
<script>on mouseUppush cdgo to card id 6003end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Dialog Name</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>In order for Dialoger to display a particular dialog for you, you must provide it information in the form of parameters. Since Dialoger is a very powerful and flexible XFCN, there are a large number of optional parameters which allow you to specify many aspects of its operation. Nevertheless, only a single parameter is strictly required. This is the Name (or ID) of the DLOG resource that you want to display. For example: put Dialoger("Example") into dResultwill display the dialog named "Example", handle the user's every wish and action until he dismissed the dialog with OK or Cancel and finally place a report of the user's selections into the container dResult. (The exact form of dResult is discussed in a later topic).</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1017</text>
</content>
<name></name>
<script></script>
</card>
card_17006.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 8388end mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>86</top>
<right>503</right>
<bottom>102</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>DLOGs & DITLs</name>
<script>on mouseUppush cdgo to card id 8500end mouseUp</script>
</part>
<part>
<id>3</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>232</top>
<right>503</right>
<bottom>248</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>Dialog Maker</name>
<script>on mouseUppush cdgo to card id 2441end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>6</id>
<text>Dialoger uses the same DLOG and DITL resources as the Dialog Manager to display dialog boxes. Therefore, before you can use Dialoger, you must have created the DLOG and DITL resources that describe how your dialog is to appear. There are two ways of doing this; using ResEdit or Dialog Maker.ResEdit is a powerful, general purpose resource editing tool distributed by Apple Computer. Unfortunately, this tool can be rather intimidating and dangerous.Dialog Maker is a built-in tool in the Dialoger package which allows you to design dialogs in HyperCard and to then turn them into appropriate DLOG and DITL resources.But don't worry… for now we'll use mine…</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>DLOGs and DITLs</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1016</text>
</content>
<name></name>
<script></script>
</card>
card_2257.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 7899end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialoger‚Ñ¢</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Dialoger is an eXternal FunCtioN (XFCN) which enables you to use real dialogs within HyperCard. With it you can display any dialog box and retrieve the results of all the user's selections. It automatically handles all the interactions with the user and returns when they have dismissed the dialog (usually with OK or Cancel).Advanced users of Dialoger may even manipulate the contents of the dialog while it is being displayed using familiar HyperTalk scripts and with the help of two more X's; dChanger and dContents. (Discussed in Section 3)Dialoger not only support all the items handled by the Dialog Manager (text, buttons, graphics and controls) but it also provides easy access to such Fancy Items as PopUp Menus and Lists (as well as some others).</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Introduction</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1015</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/7/90</text>
</content>
<name></name>
<script></script>
</card>
card_8895.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 6902end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Manager</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Control Items</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>There is actually one more kind of item which may appear in a dialog — and hence in its dialog ITem List (DITL) — a custom control. What is a control? It is a graphic object which visually conveys a value. This value may either be adjustable by the user (like a scroll bar) or it may only be adjustable by the Mac (like a progress indicator). Sometimes controls are simple and have only two values: Yes and No. The buttons we have already discussed are actually controls of this type. They are so simple, in fact, that the Dialog Manager understands everything it needs to about them.All other types of controls, however, need a CoNTroL template (CNTL) resource. This resource contains all the information necessary to display and manipulate the control (e.g. its location, size, min. and max. values, etc.).</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1014</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_2902.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 7899end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Manager</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>User Items</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Now the bad news. Remember "Fancy Stuff"? Notice we didn't mention them in our discussion of what could appear in an item list? Well, there is a very good reason for this — the Dialog Manager doesn't "do" fancy stuff such as PopUp menus and Lists.Instead, the Dialog Manager allows for one more kind of item, called a User Item. Essentially, it does nothing with a User Item except pass the buck to the programmer who is solely responsible for creating and handling the contents of the user item. It is, then only through the efforts of the programmer that we have fancy stuff in dialogs.If a dialog contains a user item, then the Dialog ITem List (DITL) contains very little information for that item. Essentially it just says: its not my job, man…</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1013</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_8500.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 3528end mouseUp</script>
</part>
<part>
<id>4</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>207</top>
<right>503</right>
<bottom>223</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>Dialog Items</name>
<script>on mouseUppush cdgo to card id 4847end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>5</id>
<text>DLOGs and DITLs</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialog Manager</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Meanwhile, back on the Ranch… we left our hero the Dialog Manager "accept(ing) a detailed description of what the dialog is to contain". Where does it get this nugget of information from? A resource, of course — well, actually two resources whose types are: DLOG and DITL.The DiaLOG resource contains information about the dialog window. This includes the window type, its size, its location on the screen and its title (if appropriate). The Dialog ITem List is a list of the items which are to appear in the dialog. Each item in the list contains the information necessary to display itself — such as its location, its size and finally, its name (for button items) or the text (for text items), or the ID of the resource to be displayed (for graphics).</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1012</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_8388.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Let's digress here for a moment to discuss resources. Resources are handy little nuggets of information which the Mac (and most applications) use in their operations. Examples of such nuggets include icons and fonts.Not surprisingly, the Resource Manager is responsible for handling resources for the system. This manager imposes order to the potentially chaotic jumble of resources in the computer by catagorizing each "flavor" of resource as a different Type which is represented by a four letter code. For our examples, the types are ICON and FONT.The Resource Manager also gives each individual resource its own Name and Number (referred to as an ID). This allows us to discuss an individual nugget with its Type and its Name (eg ICON "Next Arrow") or ID (eg ICON 3564).</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1011</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_7970.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Within every Mac sold is a wealth of built-in capability which programmers can use to make their jobs easier. It is called a toolbox. The toolbox is conceptually organized into a number of different "Managers" which are each responsible for accomplishing some set of tasks for the computer. For example, menus are all handled by the Menu Manager and fonts are all handled by the Font Manager. It should come as no surprise, then, that dialogs are handled by the Dialoger Manager.In general, the Dialoger Manager accepts a detailed description of what the dialog is to contain and then handles all the nitty-gritty of actually displaying it. While it is displayed, the Dialog Manager helps with any changes that need to be made to dialog items. Finally when the dialog is dismissed, the Dialog Manager gets rid of it.</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>The Toolbox</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1010</text>
</content>
<name></name>
<script></script>
</card>
card_7899.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cardlock screenset lockMessages to truedoMenu "Open Stack..."pop cdunlock screenset lockMessages to falseend mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>5</id>
<text>Fancy Items</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Dialogs — The Basics</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>From your experience, you probably know that many dialogs contain items other than text, buttons and graphics. Two such items are PopUp Menus and Lists.PopUp Menus act similarly to regular menus except that they appear within a dialog rather than at the top of the screen. They usually allow you to select one of a set of choices. A fine example of this is the "Open Stack…" dialog.Lists are rather self-explanatory. They are lists of information from which one (or sometimes more) "things" can be selected. Notice that while a "thing" is usually a line of text (like the "open Stack" example) it may also be something like an icon (sorry no example of an icon list).There is other fancy stuff but let's not worry about it yet…</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1009</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_7057.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Since the Mac is such a graphic machine, it would be scandalous for it not to be able to use pretty graphics in a dialog box. Actually, there are two kinds of graphics that can be displayed: icons and pictures.You are undoubtedly familiar with icons since they are used in many HyperCard buttons. They are fixed size images (32 x32) which represent an idea, operation or action. Our trusty example has run out of steam here, so instead let's take a look at the "Page Setup" dialog which contains some icons which represent the paper orientations Landscape and Portrait.Pictures are just what you might imagine. They are graphic images which can look like anything at all. They can even be in color. The tree at right is one.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1008</text>
</content>
<name></name>
<script></script>
</card>
card_6902.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Just as there was more than one kind of text item, so too is there more than one kind of button. While dialogs do not offer the plethora of button types that HyperCard does, there are still three types to choose from.Radio Buttons are named after the buttons that remember radio stations in old card stereos. They imply that only one of the choices may be selected (eg Styles in our example).Checkboxes are not so restrictive. Each one is usually independent of all others and merely lets you say yes or no to a particular option (eg Show Name in our example).Push Buttons usually provide instant gratification; they do whatever they're going to immediately. This often includes dismissing the dialog (eg "OK" and "Cancel" in our example).</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1007</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_6238.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>There are two kinds of text items: static and editable. The names are fairly descriptive in a techie sort of way.Static text simply lies there harmlessly delivering some useful tidbit of information or direction to you, the user. In our now weary example of the Button Info… dialog, the text "Card button ID: 1" is a static text item.Editable text, as you might well have guessed, is text that you can change by typing in the tried-and-true old way. Our faithful example also has one of these: the place you type in the button's name (it should contain "Button Info…" in the example).Just to confuse you, the text "Button Name:" which serves as a label for the editable text item is, itself, static text.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1006</text>
</content>
<name></name>
<script></script>
</card>
card_4847.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Obviously, there is more to dialogs than the window wrapper they come in. In order to elicit from you the information that is needed, dialogs display a number of different "things" in their window. These "things" include: • Text • Graphics • Buttons • Fancy StuffFor instance, the Button Info… dialog mentioned before has 7 Radio Buttons, 2 Check Boxes, 5 Push Buttons and 5 Text items (one of which can be edited - ie changed by the user)Notice the word "item" above. It is the correct name for each "thing" in a dialog box. From now they will be referred to as dialog items rather than "things".</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1005</text>
</content>
<name></name>
<script></script>
</card>
card_3528.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Dialogs are actually a kind of window. As such, they may choose from a number of different appearances. The most common are shown at right. The top three are designed for modal (you remember what that was, right?) dialogs. The top one is the most common by far but the others may also be used. Notice that none of them have a title bar and are not easily confused with "normal" windows. The next lower one is most often used for non-modal dialogs. It looks like a regular window largely because that is exactly what it is!The bottom window is a floating windoid — just like HyperCard's tool palette.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1004</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_3814.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>There are two basic types of dialogs: modal and non-modal. While seeping with computerese, the concept behind these terms is actually quite straightforward.A modal dialog demands that you do what it wants before you do anything else. Such a dialog will often beep at you when you so much as click the mouse outside of it. Both of the dialogs previously discussed fall into this category. Non-modal dialogs are more rare (and harder to say). They behave more like a regular window, allowing you to move them, bring other windows to the front, make menu selections, etc. Examples of this type of dialog include Search & Replace dialogs in most word processors.Dialoger actually supports 3 types of non-modal dialogs. These are discussed later on…</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1003</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_34170.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>A dialog is a displayed window when additional information is required before the Mac can do what you want. For instance, when you select "Open Stack…" from the File menu, the Mac doesn't know which stack you want to open. To find out, it displays a dialog box which allows you to select the precise stack you want to open.Dialogs are also used to group possible commands together. Consider "Button Info…" in the Objects menu above. It displays a dialog box from which you can change one or more properties of the selected button. The button at right demonstrates this.By the way, the "…" at the end of a menu item indicates that the Mac will present you with a dialog once that item is selected.</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>14</id>
<text>1002</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_60065.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 49775end mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>150</top>
<right>503</right>
<bottom>165</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>dContents</name>
<script>on mouseUppush cdgo to card id 50701end mouseUp</script>
</part>
<part>
<id>3</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>256</top>
<right>503</right>
<bottom>271</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>dContents</name>
<script>on mouseUppush cdgo to card id 53185end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>What's New</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>1.0 Compatability</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>dActivate and dBubble For non-modal dialogs, two additional XFCNs were used to support their operation: dActivate and dBubble. These two X's have been eliminated. Dialoger has incorporated the abilities of dActivate (when no parameters are passed in), and dContents has incorporated the functionality of dBubble. These changes enhanced performance and lessened the number of externals needed. However, they require that you 1) change all references to dBubble with dContents, and 2) change your idle handler to that specified in the section on Non-Modal Dialogs.dContentsWhen requesting information about the dialog as a whole, the second parameter should be 0 rather than -1 as in earlier versions. However, -1 is still supported so this change does not strictly require changing your code.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_59774.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Since this third modifier had been used to designate a pen pattern to be used for drawing an outline around the text, this capability is no longer available. Text may still be boxed using a separate UserBox. Also, line spacing of UserText items may have changed due to a correction in the way single spacing is calculated. However, the new syntax of the UserText command supports 1, 1 1/2, 2, 2 1/2 and 3 line spacing for text with the codes 1, 5, 2, 7, 3, respectively.Select / Deselect of icons and picturesIn version 1.0, the Select and Deselect commands could be used to highlight an icon or picture. In Dialoger Professional, this syntax is no longer supported as the resulting highlight was not reliable. Pictures new-found ability to become buttons allows a more effective technique — simply specify a 1x1 selection grid for the picture.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_59321.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>In the vast majority of cases, scripts written for Dialoger 1.0 will work without modification with Dialoger Professional. There are, however, some differences as noted below:userTextIn version 1.0, UserText provided a mechanism to display text in a variety of fonts and sizes. Dialoger Professional provides the StyledText command for static and editable text items for this purpose. Nevertheless, UserText user items are still supported. However, the representation of style and alignment has changed. Rather than being embedded in the actual text (e.g. <B<I for bold, italic), these attributes are included as one-letter codes in the third modifier to the UserText command (e.g. UserText Geneva, 12, BI).</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_58660.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Text items may now be made empty. The implicit item addressing scheme in previous versions meant that an empty parameter had to be ignored. This is still true of empty parameters. However, using explicit item addressing, a text item (editable or static) may be made empty. For example "7◊" as some parameter to either Dialoger or dChanger would force the text item 7 to be empty.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/22/90</text>
</content>
<name></name>
<script></script>
</card>
card_60321.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 18614end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>What's New</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Miscellaneous Enhancements:dChanger now respects radio buttion grouping. This means when changing a button to true, you do not need to explicitly make sure all others in that group are false — dChanger does it for you.Likewise dChanger now respects SingleSelection list logic. The Select and SelectText commands will deselect any previous selections as needed.Object resizing and Alignment. Objects may now be resized using the keyboard in Dialog Maker. Option-Arrow keys move the bottom right corner of the selected objects. Shift-Arrow aligns all selected objects in that direction. Option-Shift-Arrow aligns all selected objects in that direction by resizing rather than moving them.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_7452.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Additional Commands — Several additional commands have been added to Dialoger and / or dChanger: NoDismiss undoes the effect of Dismiss on a button. Height changes the height of the dialog. Width changes its width. The entire window may be hidden with the Hide command, and then shown with the Show command.A “NoSelection” logic has been added for lists for display-only lists. Also, a SelFlags command may be used by experienced programmers for total control of the selection logic of the list.A whole new complement of commands have been added to support the new constructs of Custom Controls, Picture Buttons and StyledText. </text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_58546.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Key Scrolling — List items now support “key-scrolling” for sorted single selection lists. Similar to the file selection lists, you may now type one or more characters in quick succession and have the list select the closest match. Arrow keys will also reposition the selection. This feature must be explicitly requested for a particular list and is not appropriate for lists also containing editable text.Dialog Options — Various options for the display of a dialog (e.g. hit handler) are now accessible within Dialog Maker. This allows for more complete prototyping of a dialog within Dialog Maker. In particular, a sample hit handler name will automatically be written in the card’s script. This script may be refined and tested all within the Dialog Maker environment before exporting. The exported button carries the hit handler with it for single click installation into the destination stack.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_59128.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 50384end mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>75</top>
<right>503</right>
<bottom>90</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>Item Addressing</name>
<script>on mouseUppush cdgo to card id 52012end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>What's New</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Unlimited Item Addressing — Commands to Dialoger and dChanger are no longer restricted to the implicit mapping of parameters to items. While this syntax is still supported, any command may be preceeded by an item number and then a “◊” (option-shift-V). Stack Index — A floating windoid of all dialog resources currently in the Dialog Maker stack keeps an index at your fingertips. From this windoid, a dialog’s card may be selected (by clicking), a new card created, or an existing dialog deleted. The contents of any dialog may also be viewed as a numbered list of items for quick reference.Version reporting — If a “◊” is passed in as the one and only parameter to Dialoger (or any of the other X’s) version information will be returned.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/21/90</text>
</content>
<name></name>
<script></script>
</card>
card_57978.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Floating Palettes — Dialoger now supports an additional way of displaying dialogs entitled “float”. These windows will remain above the card window at all times. Most often this feature is used in conjunction with tool palettes. Other items, such as lists and popup menus may also be included in a palette — indeed anything may (except editable text). Styled text with scrollbars — Static and editable text items may now include a scrollbar. They may also have their own text style including font, size, style, alignment and line spacing.Picture Buttons — A single picture may be divided into a two dimensional grid of buttons. Two kinds of selection logic are supported for these buttons 1) radio button and 2) push button.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_51615.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 34170end mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>236</top>
<right>503</right>
<bottom>251</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>Custom Controls</name>
<script>on mouseUppush cdgo to card id 37397end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>What's New</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Intro</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Dialoger Professional for Microphone has been updated in a number of exciting areas. They are summarized on the following pages for users of version 1.0 of Dialoger and Dialoger Developer. If you are a new user of Dialoger, however, these brief highlights will not mean much to you. Instead, you should skip ahead to the section Digging In.And the enhancements are:Custom Control Items — Dialoger now supports the inclusion of custom controls in a dialog. The standard controls (push button, radio button, checkbox and scrollbars) are included as are any custom controls in the stack (CDEFs). A wide selection of read-made CDEFs have been included for use in any dialog.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>9/24/91</text>
</content>
<name></name>
<script></script>
</card>
card_44252.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cdgo to card id 34170end mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>209</top>
<right>503</right>
<bottom>225</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>“Getting Fancy”</name>
<script>on mouseUppush cdgo to card id 18049end mouseUp</script>
</part>
<part>
<id>3</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>403</left>
<top>269</top>
<right>503</right>
<bottom>285</bottom>
</rect>
<style>rectangle</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>italic</textStyle>
<name>Dialog Maker</name>
<script>on mouseUppush cdgo to stack "Dialog Maker"end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Welcome</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Nevertheless, to get the most out of your investment, you will want to learn more about the world of dialogs.The next section in this stack, “Digging In” provides an in-depth discussion of not only Dialoger but also the underlying concepts associated with dialogs in general. After completing it, you will be able to design, create and use complex dialogs within HyperCard.As your needs (or curiosity) progress, Section 3 “Getting Fancy” reveals the full power and flexibility of Dialoger. After completing this section, you will be able to take full advantage of all the components of the Dialoger package.By the way, the Dialog Maker stack provides ready-made dialogs which might fit your needs right away…</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Do What, When?</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>3/20/90</text>
</content>
<name></name>
<script></script>
</card>
card_43652.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpset lockmessages to truelock screenset icon of me to 978select medoMenu "copy button"go homedoMenu "paste Button"choose browse toolunlock screenput "cd btn"&&(number of cd btns) into objset name of obj to "Dialog Maker"set script of obj to ¬"on mouseUp" & return ¬& "go"&"e&"Dialog Maker""e&return ¬& "end mouseUp"put "Move mouse to desired location and click."repeat until the mouse is downset loc of obj to mouseLoc()end repeatlock screengo backset icon of me to 18630put emptyunlock screenset lockmessages to falseend mouseUp</script>
</part>
<part>
<id>4</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>412</left>
<top>145</top>
<right>489</right>
<bottom>205</bottom>
</rect>
<style>transparent</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>18630</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Install Resources</name>
<script>on mouseUplock screenset lockMessages to truego homeget long name of this stackdelete word 1 of itdelete char 1 of itdelete last char of itput it into toFilego backset lockMessages to falseunlock screenget long name of this stackdelete word 1 of itdelete char 1 of itdelete last char of itput it into fromFileput number of lines in cd fld "ResourceList" into rCountrepeat with l = 1 to rCountget line l of cd fld "resourceList"put item 1 of it into theTypeput item 2 of it into theNamerescopyquick fromFile,toFile,theType,theNameProgress theType&&theNameprogress trunc(l*100/rCount)if the result is not empty then answer the result with "Continue"end repeatprogress "dismiss"answer "Resources sucessfully installed. Quit now." with "Quit"doMenu "quit hyperCard"end mouseUp</script>
</part>
<part>
<id>5</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <true /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>394</left>
<top>17</top>
<right>513</right>
<bottom>342</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>9</textSize>
<textStyle>plain</textStyle>
<textHeight>10</textHeight>
<name>resourceList</name>
<script></script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Welcome…</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>Going Places</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>Since Dialoger promises to become a vital part of your computing life, you will want to install a button in your home stack to bring you directly to the Dialog Maker stack. Click on the button at right to install such a button.Also, let's install some resource in your Home stack. This step allows us to use dialogs in any stack without having to load that stack down with the X's needed to actually display the dialog (although it will still need the actual dialogs). You should quit HyperCard immediately after this step to enforce the changes. Then relaunch HyperCard and return here. Once you have done that, you are ready to get started. If you are the type of person who reads the last sentence of a novel first, then the Dialoger Maker button on the lower left will tell you whodunnit. For the rest of us, let's proceed a little more slowly.</text>
<script>on mouseUppush cdgo to card id 56551end mouseUp</script>
</part>
<content>
<layer>background</layer>
<id>4</id>
<text>Welcome…</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>The Stacks</text>
</content>
<content>
<layer>background</layer>
<id>6</id>
<text>As you have undoubtedly noticed, there is an area to the right of this text which often contains pictures and other such graffiti. Depending on the card, some other interesting things might appear in this space.For example, the stack is lettered with buttons which help illustrate the technique being described in the text. These buttons look amazingly similar to the one at right (although their names may be changed to protect the innocent). When such things are encountered, it is best to say a short prayer and give them a click. If your adventurous, you can peek at their script by command-option-clicking on them.Buttons such as those at right will instantaneously take you to a card which relates to the topic at hand. When you have absorbed this related material, use the Return arrow button to get yourself back on track.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_56551.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Along the bottom of each card are navigation arrows which allow you to move from card to card. When you are ready to move on, click the right-facing arrow. When you want to review a previous card, click the left-facing one.The Return arrow in the lower righthand corner allows you to pick up where you left off if you start wandering off into cross-references (described soon, I promise).Meanwhile, lurking in the lefthand corner are two buttons, one to take you home at any time (The Dorothy Memorial Home Button) and a button to take you to Dialog Maker — the workhorse of the product.Finally, there is a big button to the right of the Topic / Subtopic Headings which will take you back to the first card which serves as a table of contents to all the topics.</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_34913.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text>Welcome to Dialoger. Your package consists of two stacks; Dialog Maker and Dialoger Help.Dialog Maker — the design environment for the creation and manipulation of dialogs. This is where you will “work”. As you may know, previous versions of Dialoger contained two additional stacks; Dialoger Commands and Dialoger Examples. These have been integrated into the Dialog Maker stack for your convenience).Dialoger Help — this stack. It combines both an interactive tutorial and an in-depth information source for dialogs in general and the Dialoger product in particular. The next card tells a little more about how to use this stack so click the right arrow (below) when ready…</text>
</content>
<content>
<layer>background</layer>
<id>4</id>
<text>Welcome…</text>
</content>
<content>
<layer>background</layer>
<id>5</id>
<text>The Stacks</text>
</content>
<content>
<layer>background</layer>
<id>12</id>
<text>1.0</text>
</content>
<content>
<layer>background</layer>
<id>19</id>
<text>4/11/90</text>
</content>
<name></name>
<script></script>
</card>
card_5336.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
